#ATLASSIAN GIT FOR WINDOWS HOW TO#

The -stat option displays the number of insertions and deletions to each file altered by each commit (note that modifying a line is represented as 1 insertion and 1 deletion). Two of the most common options are -stat and -p. The git log command includes many options for displaying diffs with each commit.

The second commit has another branch pointing to it called feature, and finally the 4th commit is tagged as v0.9.īranches, tags, HEAD, and the commit history are almost all of the information contained in your Git repository, so this gives you a more complete view of the logical structure of your repository. This lets you know that the top commit is also checked out (denoted by HEAD) and that it is also the tip of the main branch. Your typical git log -oneline output will look something like this:Ġe25143 (HEAD, main) Merge branch 'feature' ad8621a (feature) Fix a bug in the feature 16b36c6 Add a new feature 23ad9ad (tag: v0.9) Add the initial code base By default, it displays only the commit ID and the first line of the commit message. The -oneline flag condenses each commit to a single line.

#ATLASSIAN GIT FOR WINDOWS HOW TO#

Please see in The git config Command for how to set up an alias. If you don’t like the default git log format, you can use git config’s aliasing functionality to create a shortcut for any of the formatting options discussed below. Most of these come in the form of flags that let you request more or less information from git log. Formatting Log Outputįirst, this article will take a look at the many ways in which git log’s output can be formatted. Together, these two skills give you the power to go back into your project and find any information that you could possibly need. The advanced features of git log can be split into two categories: formatting how each commit is displayed, and filtering which commits are included in the output. But, you can alter this output by passing many different parameters to git log. That’s where the git log command comes in.īy now, you should already know the basic git log command for displaying commits. But, having all of this history available is useless if you don’t know how to navigate it. This gives you the power to go back into your project history to see who contributed what, figure out where bugs were introduced, and revert problematic changes. The purpose of any version control system is to record changes to your code.

Atlassian git for windows