So this post is here to play devil's advocate, and argue against the CLI for your primary Git usage. I certainly know Git very well, and honestly think I'm far faster and more efficient in a Git GUI than I could possibly be on the command line - and I'm certainly not slow in the CLI. Whilst I understand the reasons given, I also think it's a huge generalization that unfairly sees Git GUI users as unlikely to really understand Git properly. It’s a shame that there are no options for in-editor Git clients.I quite often hear experienced Git users say that you should always use the command line for Git, and you should try to avoid using Git GUIs. Picking a Git Client for Unity ProjectsĪfter testing several Git clients, my current choice is split between the Git command line for most tasks and Fork (with SourceTree as a solid backup) for tasks that require a bit nicer visualization such as reviewing large commits. On the other hand, having a well-supported product is also nice, so I might look into one of these options at some point in the future. Since my indie-development is a pretty slow process, I like to avoid as many subscription-based products as possible. GitKraken runs on Windows, Mac, and Linux and has a lot of great features, but it costs $69 per user per year for their Basic plan, and it runs on Windows and Mac. Git Tower / Git Krakenįinally there are a couple of paid Git clients that are worth looking at. There are several other nice features in Fork, so check out itsīlog if you decided to give it a try. Since I tend to close my Git client when I’m done using it, this is certainly a bonus. On my relatively small game project, Fork launches and opens my repository about 4 to 5 times faster than SourceTree (and uses about half as much RAM). One thing that did impress me with Fork was its performance. There are some new image comparison features for LFS tracked files in the Mac version that look useful, but sadly updates to the Windows version seems to lag behind a bit. It offers side-by-side diffs which I like a lot more than the standard diff style (although that is an option as well) and both a light and dark UI theme. It has a nice, clean interface that is similar to SourceTree’s. Forkįork is a relatively new Git client for Mac and Windows that can be evaluated for free, but costs $49.99. Branching, merging, and stashing are all straight forward and work well. It’s History view makes it easy to keep an eye on past commits, and I’m a fan of the No Staging option in the File Status view. I’ve used it for different projects over several years and, while not without its quirks, I think it’s still one of the best (free) clients available for Windows and Mac users. So for now, it appears that we’re left using one of the following general-purpose Git clients. Git-for-unity fork, but sadly nothing in the last 7 months. It does appear that there is still some work being done in this It’s free and open-source, but sadly it has now beenĭeprecated. When it first came out I was quite excited by the prospect of a nice, in-editor Git client. GitHub for Unity can be used with non-GitHub repositories. In the following sections, I’ll cover a few that I’ve tried and which work best for my workflow. There are times when a nice GUI can come in handy especially when browsing the commit and branch history. So far, it hasn’t been a huge issue as I just leave MinTTY running, but it’s something to be aware. If certain applications like VS Code are launched from it and then MinTTY is closed, it will fail to restart until those applications are also closed. Lately, I’ve been using the other option, MinTTY, which works quite well but has the opposite issue. In the past, I’ve used the Windows console option (cmd.exe), but it had an annoying issue that would cause me to have to restart it every so often. I’ll cover several of mine in the next article as well.ĭuring the Git installation (for Windows), it offers the choice of two terminal emulators to choose from. Luckily it’s possible to assign new aliases in Git, which makes it easy to come up with a relatively short list of custom commands to use for most tasks. Stack Overflow questions and answers to get help when using it.Įven with all the help out there it can still be a bit overwhelming at first due to the myriad of Git commands available. Most tutorials also use the command line, and there is a near-endless supply of I find it easier to set up the initial repository from the command line and perform quick commits. Git command line client at certain times when working on a git repository. In this article, I’ll review a few of the options that I’ve tried while working on past projects. One of the nice things about using Git for version control on a Unity project is the large number of free and paid clients to choose from.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |