For the most common and simplest Git commands, such as Git commit, Git branch, Git checkout, Git pull, Git push, or Git merge, GitHub Desktop does pretty well. And let’s give credit where credit is due GitHub Desktop is a huge step up from the CLI for many users, especially for those who have never touched the terminal before.īut in trying to provide a path around the CLI, GitHub Desktop seems to embrace some of the limitations of the command line, especially around visualizing version history and branch management. In 2017, GitHub redesigned the application and released it as an open source project called GitHub Desktop 1.0. In an attempt to answer this need, they introduced their Git GUI in 2015: GitHub Desktop.
#Github desktop cherry pick code#
Introducing GitHub DesktopĪ few years back, the GitHub team realized that many of their beginner level users were having issues with learning Git via the command line and getting their code pushed to GitHub. And lest we forget, collaboration is one of the founding goals of Git itself. With that being said, is the most popular way to distribute Git repositories worldwide, with millions of developers using the tool to collaborate with others. But you do not need GitHub to leverage Git. It is absolutely true you need Git-the open source version control tool created in 2005-to use GitHub. It is very common for beginning developers to encounter both of these ideas at the same time and, as a result, perhaps get confused that you need one to use the other, or may even think they’re the same thing.
It’s so nice visualizing the branches, changes, commits, and being able to work my entire Git flow through a beautiful GUI.” – vs GitHubįor many, GitHub is synonymous with using Git.
0 kommentar(er)
