![]() ![]() Very finicky, with multiple steps to add a submodule and having to manually edit a configuration file to remove a submodule. ![]() Submodules, I think, are a weakness in git (the "pure" git, with the CLI, not Git Extensions). One thing I'm particularly impressed by is the way Git Extensions handles submodules. For an example, take a look at the Pull dialog box which includes diagrams of what the different merge options do. The developers have done a really good job of packing so much functionality into the application, in a clear and understandable way. I've been impressed with how much I can do with Git Extensions. That's not entirely true but I only have to use the CLI about once a month or so, for really obscure and tricky stuff. The developers claim that Git Extensions allows you to do everything via the GUI, that you never need to drop down into git's command-line interface (CLI). So that's what I didn't like about the other Git clients for Windows. It's in its early days so may be worth looking at in a year or two but, for the moment, Git Extensions is far more powerful. Source Tree is beautiful to look at, much more polished than Git Extensions, but I found it lacks some of the functionality of Git Extensions. This would be fine for people who host their remote repositories on GitHub but I was looking for something to use at work, where the remote repositories are hosted on our local network. While it could be used with repositories that weren't hosted on GitHub, it seemed to me the assumption was that many functions would be carried out on the GitHub website so that functionality was not included in the client. The GitHub Client for Windows was too basic for me. I came to the GitHub Client for Windows and Source Tree after having used Git Extensions for a year, just to try them out and see if they were an improvement on Git Extensions. I didn't like the workflow with TortoiseGit, which seemed to me to be trying to fit a square peg into a round hole: It seemed to be a port of a version control system (VCS) that deals with changes at a file level, such as SVN, and didn't really seem designed to deal with a VCS like git that deals with changes at a project level (with each commit being a snapshot of all files in the project). The GUI for Git for Windows handled the basics but for anything more you have to drop into the command-line interface. ![]() Git Extensions was one of five git clients I tried for Windows: Git for Windows (which has a basic GUI), TortoiseGit, GitHub Client for Windows, Source Tree (from Atlassian, the people behind BitBucket) and Git Extensions. Not having used git before I was looking for something with a GUI so I wouldn't have to remember all the commands and options. Tl dr: For those who don't want to read the rest of this review I tried five git clients for Windows and found Git Extensions much better than any of the others. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |