Oftentimes, the CLI’s side claims using this method can give you access to all of the fine features offered by git where a GUI may fall short. This argument can at times come with a little heat, and as with most arguments, there are valid points to each side. SourceTree, GitKraken, Git Cola, Github Desktop, or SmartGit are a few of the names you may be familiar with already. or even integrated into other tools you may already use. These can be presented as its own program. GUI – “Graphical User Interface.” Rather than using the terminal, a GUI will show the repo and git commands with more visual aspects and become more interactive for the git user. Using the CLI rather than a GUI provides a lot of value: seeing the bigger picture of your code and being able to navigate through different branches, commits or history can become clean and easy to understand with a little help from your friendly GUI.Īs a recap on what each term means, here is a description of git, CLI and GUI:ĬLI – “Command Line Interface.” When using the CLI, the git user will be interacting with git and their repo through the command line on a terminal, with commands given and information seen in the terminal as well. While not the popular opinion of CLI git users, I’ve gotten a ton of mileage from my git GUI.
0 kommentar(er)
