However, it does help understand at a fundamental level what is going on internally when you need to do heavy problem solving. Two examples of GUIs for Git are GitHub Desktop and GitKraken. I mean, I learned assembly and memory addressing in college, but that doesn't really apply to high-level languages directly. Some of us just really like to know how stuff works. git folder, then I suppose you don't really need to know that stuff, but to me it is a lot like asking "why do I need to know how a combustion engine works when all I have to do is turn the key?" The most important reason people chose SourceTree is: In addition to color-coded branches and icons that tell if a file has been added, removed or modified, SourceTree also displays the number of commits that are ahead and behind the remote branch. If by "bits and bytes of Git" you actually mean understanding how the files, blobs and trees work inside the. SourceTree is ranked 8th while GitHub Desktop is ranked 14th. Though I do agree that for seeing a diff of what files has changed, or selecting only a few files to commit with checkboxes, a UI tool can be easier (I frequently use SourceTree to visually review changes, and the command line for checkouts, branching, merging, etc). Best Free: Sourcetree, Git Desktop (For GitHub users) Both are free. That would be my argument for learning at least some Git command line. The following are some suggestions for Git GUI Clients based on Cost and, Os compatibility. For example, last time I used it, you couldn't stash, cherrypick merge, commit amend, manage remotes, etc. It is just a UI around the most common Git commands.
#Github desktop vs gitkraken windows#
GitHub for Windows can't do everything that command-line Git can. By "GitHub Desktop Interface" I assume you mean "GitHub for Windows".
0 kommentar(er)
