Jump to content

Search the Community

Showing results for tags 'github'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Plastic SCM
    • General
    • Installation and configuration
    • Unity 3D
    • Plastic SCM on Mac
    • Plastic SCM on Linux
    • Gluon
    • Git interop
    • Integrations
    • Community Edition
    • Branching and merging
    • Announcements
  • Plastic SCM 4.0 Beta (Closed)
  • Plastic Cloud
    • General
    • Configuration
  • SemanticMerge
    • General
    • License
    • SCM's configuration
    • Share your experience!
    • External Parsers
  • GitJungle
  • Method History for Subversion

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 10 results

  1. Hello everyone, I'm new to plasticSCM and I'm trying to sync my github repo to be able to fully work on plasticSCM in the future. There is one problem with Git LFS while following the sync guide in the last part of the export I got the following message : "An error occurred while contacting GitHub LFS: This repository is over its data quota. Account responsible for LFS bandwith should purchase more data packs to restore access.. You can disable the Git LFS support from the command line (cm syunc) unsing the '--skipgitlfs' option." I went on Github to buy more bandwith on LFS w
  2. Hi, We have the repository that is hosted in PlasticSCM Cloud. It is small repo without huge files. I need to sync it with new GitHub repository. I open Repositories, click "View branches" on the repository Repo@Company@cloud, and then run "GitSync..." at the main branch (result doesn't depend on the particular branch). The PlasticSCM client executes all steps and at final step shows the following message: "Unable to read data from the transport connection: The connection was closed". plastic.debug.log.%date%.txt includes the following lines: Error message: Unable to read d
  3. I have a Github repository that I'm trying to sync with my Plastic repository, but I only seem to be able to sync one way. My first sync works only if I don't put in a username/password, and I can successfully sync the Plastic repo with my Github repo. However, when I check-in a change and then try to sync with git again, I always get the error "The credentials introduced for this repository are not valid". This is true not matter what I put into the username/password boxes, even if they remain empty as before. Now, I assume that the username and password asked for are the u/p combo I use
  4. Hi everybody, I'm afraid I did a big mistake on one of my repo. I have a repo called "My_repo_A" which has a XLinked sub repo called "My_repo_A_shares". This sub repo "My_repo_A_shares" is synced with a repo on github. But tonight, after a hard work week, I synced by mistake the parent repo "My_repo_A" with the same repo on github. That resulted in a warning like "the branches have to be merged before being able to push with gitsync again ...". Hopefully there are no problems on github, but in plastic a lot of commits are duplicated with different guid, and branches have two hea
  5. Hi! We are making games and would like to have Github repos in sync and inside our Plastic Cloud repo: Example: -our_repo // on Plastic Cloud --Assets ---Addons ----Postprocessing // that is synchronized with Unity Technologies repo on github Looking at the documentation and dozens of forums and blog posts, I'm still unable to get it working: Using Sync With Git on a branch throws an error; The changeset (...) could not be imported (...) An implicit transaction is not supported to write the metadata (...) Creating an xlink using a GitHub server doesn't wor
  6. Hi Everybody I'm trying to Sync with a private Github repository (I can access it because it is shared with my Github account). The username and password I entered are correct but this gives me the following error : An Error occured while connection to git : impossible to create SSL/TLS secured channel I use plastic 6.0.16.1765 I can give the Github repo address because it's confidential. Any Idea ? Thanks by advance.
  7. I'm trying to sync my Plastic repo with a Github repository and I'm finding a strange behavior. If I try to sync from my laptop or workstation, I get this error (run from the command line): So it can connect to github but can't seem to pull the changes. The strange part is that when I logged into the machine my Plastic server is running on (Linux) and run the same command, it works great! So I'm halfway there, but it would be nice to be able to sync with the GUI and not have to log into that server. I think, but I'm not certain it's related, that the error on the server
  8. I had syncing working perfectly from work. I came home and now whenever I try a replication->sync with git it says "Receiving references: ok" but then I get an error that says "The underlying connection was closed. A conenction that was expected to be kept alive was closed by server." Help?
  9. I've got Plastic nicely talking to Github as a back end repo. Once I figured out where the controls where it all went very smoothly. Kudos on that. One question: Git hub has an issue tracker for their projects. I didnt see it listed on the web page that talks about using issue trackers with the Plastic client. Is it integrated? If so, where might the setup instructions be hiding? Thanks ProfK
  10. Hi guys, I'm trying to sync with a GitHub private repository (which I have access to, but I'm not the owner), and I'm having this error saying that The Credentials introduced for the repository are not valid. I've tried using my GitHub credentials in the Username/Password fields. In the plastic.server.log file I see this line when the problem happens: 2015-02-27 19:54:13,070 (null) NT AUTHORITY\SYSTEM at (null) INFO Channel - conn 2. Tcp transport error. Connection closed Any ideas on this? Thanks in advance
×
×
  • Create New...