Over a million developers have joined DZone.

Git tutorial – comparing files with diff

DZone's Guide to

Git tutorial – comparing files with diff

· DevOps Zone ·
Free Resource

In response to accelerated release cycles, a new set of testing capabilities is now required to deliver quality at speed. This is why there is a shake-up in the testing tools landscape—and a new leader has emerged in the just released Gartner Magic Quadrant for Software Test Automation.

Continuing from my last post, which explained my Git workflow, in this post I’m sharing how to compare different versions of files. Before that, you might want to read the Getting started with Git post too if you haven’t done already.

The main objective of version controlling is to enable you to work with different versions of files. Git provides a command diff to let you to compare different versions of your files.

The most common scenario to use diff is to see what changes you made after your last commit. Let’s see how to do it.

I opened the helloworld project from my last example with a clean working directory. i.e. I have already committed all my code changes. So, a git status will give an output like this:

C:\vraa\projects\helloworld> git status
# On branch master
nothing to commit (working directory clean)

Let’s make a change in the helloworld.txt file now and compare this file with previously committed version.

C:\vraa\projects\helloworld> edit .\helloworld.txt
C:\vraa\projects\helloworld> git diff HEAD .\helloworld.txt
diff --git a/helloworld.txt b/helloworld.txt
index e4f37c4..557db03 100644
--- a/helloworld.txt
+++ b/helloworld.txt
@@ -1 +1 @@
-Hello India
+Hello World

There it is. Git shows the exact change I made in the file. But, if you look at the diff command, you might wonder what HEAD is doing there! Well, it is there for a purpose.

If you can recall, Git has an index between local repository and your working directory. So most of Git commands can either refer to index or the local repo. When you say HEAD in your Git command, it refers the local repo.

git diff HEAD [filename] //  compare the working directory with local repository.
git diff [filename] // compare the working directory with index.
git diff --cached [filename] // compare the index with local repository.

You can also compare files between two different commits. Every commit in Git has a commit id which you can get when you give git log. Then you can use the commit id if diff command like this.

git diff 7eb2..e03 812...a3f35

You can compare not just a single file, but all your changes at once. If you made changes in many files, just don’t mention any file name in the diff command which will diff all the changed files.

git diff // compares working directory with index, i.e. shows the changes that are not staged yet.
git diff HEAD // compares working directory with local repository. shows the list of changes after your last commit.
git diff --cached // compares index with local repository. shows the diff between your last commit and changes to be committed next.

That’s it about the basic introduction to compare files in Git. If you have any comments about this series, do let me know. I’ll continue with other topics in my next post.


From http://veerasundar.com/blog/2011/06/git-tutorial-comparing-files-with-diff/

Gartner: Digital Transformation, DevOps, and the Future of Testing. Download Now! 

java ,version control

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}