On the top right of the window, there’s the Fetch Origin option, which gets the latest commits from your origin remote. To change your current active branch to a different one, simply select a new branch from the list of branches. It will be created from the current active branch. To create a branch, click on the Current Branch tab and enter the name of the new branch. Let’s move on from comparing branches to creating or changing a branch. On selecting a specific commit, you’re shown the changes that were made in that commit: On selecting Show History from the View menu, you’re shown the commits in the active branch. The workflow in the current branch is shown at the top. If any commit is selected, the commit details are shown too. Once a repository is selected, the commits in the current branch are listed. If you add a GitHub repository, it will be listed under your username on GitHub, whereas if you add a local repository, it will be listed under Other. Once you’ve added your repository, you’ll notice that it’s now listed among the tracked repositories in the repositories list ( Current Repository tab, top-left). You’re then asked to select the path to an existing Git repository on your local system. Select the repository you want to clone, and click on Clone to clone it.Īlternatively, you can add a local Git repository by choosing the Add Local Repository… option in the File menu. You can also see a list of your repositories under the Clone Repository… option.
You can create a new repository through the New Repository… option from the File menu. When you successfully log in to your account, all your repositories are linked to your GUI tool. Although a bit confusing, you can even manage Bitbucket repositories through the GitHub GUI tool! You can manage other local Git repositories with GitHub Desktop too, but it’s tailor made for GitHub repositories.
#Git gui client atlassian windows
The Windows and macOS versions of GitHub’s previous clients differed, but in August 2015 GitHub launched GitHub Desktop as a new, unified client for both platforms.Īfter installation, you should add your GitHub account details. Let’s first take a look at the GUI client of GitHub itself. Note that Git GUI tools frequently change their UI, so the screenshots below may differ a little across versions and operating systems. I’ll now look at GitHub Desktop and Sourcetree in turn, evaluating their features and ease of use. I suggest using a combination of GUI tools and the command line, utilizing the advantages of each.
This is problematic if you find yourself in an environment without GUI software, or if you need to run emergency commands from the command line-such as working on a remote server. One issue with using GUI tools is that it’s easy to forget proper Git commands. Though we arguably gain a deeper understanding of Git by learning it through the command line, GUI tools have their place, especially in simple situations. GUI tools are an attractive option to many developers, as they provide an easy interface for managing a project with Git. Visual Studio’s version control tools enable you to integrate with multiple version control systems to manage repositories hosted in remote locations.
Sublime Text’s Git Integration package enables the use of many Git-related features from within the confines of the text editor. Atom, a text editor by GitHub, has built-in Git and GitHub functionality. You can also use Git’s capabilities through extensions in your text editor.
#Git gui client atlassian trial
All of these applications are either free or have free trial versions. Other popular GUI clients are Tower (macOS), GitBox (macOS), SmartGit (Windows, macOS, Linux), Fork (Windows, macOS, Linux), and GitKraken (Windows, macOS, Linux). Both of these applications have macOS and Windows versions, but neither supports Linux. First, we’ll review GitHub Desktop, GitHub’s own GUI tool, and then Atlassian’s Sourcetree. In this chapter, we’ll look at the GUI tools that serve as Git clients. For these reasons, I’ve avoided the use of Git GUI tools so far. GUI tools also lack some of the power and features of the terminal, and terminal commands execute more quickly.
Although GUI tools can appear to make life simpler, applications can use differing UIs, terminology, and Git concepts. In Chapter 1, I mentioned that there are various GUI (graphic user interface) tools that can be used instead of the terminal. The advantage of terminal commands is that they work across all platforms. Until now, we’ve performed all our Git-related actions through the terminal, looking in detail at what each command does.
0 kommentar(er)
