#Gitkraken file change how to#

With all three of these types of changes, nothing is ready to commit until we вЂњstageвЂќ them. If you delete a file that was previously being tracked.

If you add a new file to the repository (that isnвЂ™t being ignored by git - weвЂ™ll dive into git ignore files soon, too!), it will simply exist on disk, and git will know itвЂ™s new, but again if you commit now, nothing would actually happen.

We have to tell git that the changed file should be committed by вЂњstagingвЂќ it. If you were to perform a commit on the repository right now, nothing would actually happen.

When you make a change to a вЂњtrackedвЂќ file (a file that has previously been committed to the repository, for example, a file that you received during the cloning process), it simply exists in a changed state on the file system and git knows it changed.

There are three primary reasons you might need to вЂњstageвЂќ a file: LetвЂ™s get an idea of what it means to вЂњstageвЂќ (or вЂњunstageвЂќ) your changes in a git repository.

#Gitkraken file change how to#

In this post, IвЂ™m going to show you how to add and remove files - or, in git lingo, stage and unstage files. However, just editing or creating files in the repository doesnвЂ™t necessarily mean theyвЂ™ll be committed, pushed (future topics, I promise), and available for other folks to work with. Now that we have a repository to work with, we need to make some changes! Maybe that involves changing existing files, or adding new ones. In my previous post, вЂњ GitKraken Git GUI How-To: Cloning a RepositoryвЂќ, we went over how to do just that.