Search the Community
Showing results for tags 'git'.
Found 4 results
I'm exploring using Plastic for a monorepo I manage that is getting a little large for git. However, when I run fast-import, then open a workspace showing the paths that LFS was used on, I only have the LFS marker files, not the large binaries themselves. What's the best way to do this (one time) import?
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 to log on to Github. But it's not working. Why? How can I fix this? The repo I'm testing: https://github.com/aormsby/LittleTools-Unity.git
Hi, I'm hoping I can receive some fairly urgent help with this one. I'm having problems syncing to my git repository (where I have paying customers waiting for updates). When I tried to sync this afternoon I received the following error "An error occurred processing your request" but no other information as to what that error might be. I can sync up other plastic repositories to their git equivalents ok. I've taken a look at the plastic log and the only thing that look suspicious is the last line which reads: 2016-06-06 17:41:09,850 (null) NT AUTHORITY\SYSTEM at (null) INFO Channel - Connection 2 from 127.0.0.1 closed I've attached the full log for you to take a look at though. Let me know if you need anything else from me. Thanks, Tom plastic.server.log.txt
I have been using the 4.2 development branch and successfully using git sync to sync Plastic and Git. Up until yesterday, I was using 188.8.131.527 and all was working fine. Yesterday, I upgraded to 184.108.40.2069 and now I am unable to get the git sync to work properly. The error message simply states "The branch attribute is not correctly formed", with no explanation of which branch or why such a branch might not be correctly formed. I'd review logs files to see more, but I don't know how to turn on the logs for the client side. Please advise as to next step for further research? Thanks, Stuart.