Once your repository is initialized and the interface is out of the way, it’s time to get cracking … Whaahh-pssh! … and tie all of the interface and concepts together to perform work on your repository. When you change branches, pull in changes, or reset, GitKraken Client will update the files in the working directory to reflect the changes.įor more information on Git repositories, check out the Git repository tutorial blog post including a video from one of our developers. The working directory is the currently checked out version of the files in the local repository. This contains all of the information required for the Git repository and if this folder is deleted, you would no longer be able to switch branches, pull from remotes, or view commit history. When initializing a Git repo or cloning from a remote, you will notice a.

It also means if there is a catastrophic event on the remote server, or if another user makes an unwanted change on a remote, all of the other members of the team would still have a copy of the full repo so it can easily be restored.git folder The local repository includes all of the branches, and changes made to the repo, since the time it was created.īecause you make a copy of the entire remote repo, you can change branches, view history, and commit changes without needing a network connection. One of the reasons why Git is so fast when compared to other SCM tools is because all changes are made locally rather than on a remote server. You can easily identify any local branches in the graph as they are shown with the icon. Most of the work you do in GitKraken Client is using the local repository, meaning the files and changes are saved on your local machine.

The beginner's guide explained download