Resolved Unity version control does not support Git

The documentation has a page Unity version control for Git users, but no instructions on how to set this up (to my knowledge, Unity version control was Plastic SCM-only).

I'd be really excited to use this with GitHub! Is it possible, and how so?

 

Hey Casey, it's Dylan
This page is to show how common git actions are called in Plastic for those starting out with plastic after using git. UVC does not support git and I doubt it ever will

 

Ehmmm both download links are down

 

https://github.com/spoiledcat/git-for-unity

This is the non deprecated one

 

Thanks, I tried git for unity but it was overall a horrible experience, nothing gained over using a git client. I just misunderstood the title.

It's a shame, I have worked with Plastic SCM before and it's a great experience. But I'm not yet working on long-term projects so then paying for Plastic seems a little excessive. Maybe one day when I'm earning more comfortably!

 

Yes I do, but it always seems like I either work in teams of 10 or in teams of 1

 

To be fair, Unity's in-engine Unity Version Control package is equally horrible. Resource hog, wrong entries in change lists, hard to maintain. The proper way to use version control is to use the standalone app or command line anyway. Especially because you can store raw assets, 3rd-party assets (like FMod project) and whatnot in the same repo this way.

 

I also like to add custom packages in the form of sub modules so I can keep working on them within the context of the current project.

But if we’re being real then games and version control just don’t gel together, AT ALL! The only real solution I think is to have the project hosted on a server somewhere and have everyone access the same copy, kinda like how Google Drive works. I know there is a company that does this but then you are REALLY payin’ top-dollar.

 

Not belaboring anyone, but artists, programmers, designers and composers I’ve learned have very different ideas on how to organize a scene and somehow, somewhen, we always manage to break it in such a way that 2 people on HEAD do NOT have the same copy of the same scene. You try rebasing and making new branches until you eventually say “duck it, one of you is gotta do a clean install of this repo”.

Also the reason why I think Plastic is nicer, but I haven’t used it that much so you probably have stories from the trenches that will scare me straight too.

 

Tbh games in plastic (did not use the unity package) worked great with a small team in the free tier. No issues with large files etc
Think it also supports file locking so no one else can touch a scene when they work on it, but not fully sure

 

After our last project I'm still learning more about collaborating in Unity.

I thought people here would also be interested in this thread I made called "Why working in Unity isn't like Google Drive". Because really: why isn't it?
https://forum.unity.com/threads/why-working-in-unity-isnt-like-google-drive.1449805/

(Disclaimer I know very much why it isn't just, but I still think it's an interesting topic to discuss.)