git see changes

New Era

2 min read

·

19-10-2024

91

0

Share

Uncovering the Mysteries: How to See Changes in Git

Ever felt like you're lost in a maze of code, unsure what you've changed or what's changed around you? Fear not, Git has you covered! Understanding how to see changes in Git is crucial for efficient development and debugging. This article will guide you through the essential commands and tips, all sourced from the vast knowledge base of the GitHub community.

The Fundamental Commands

Let's begin with the foundation:

1. git status - The First Glance:

git status

This command is your first port of call. It provides a snapshot of your current branch, telling you:

• Untracked Files: Files you haven't added to Git yet.
• Changes Not Staged for Commit: Modified files that haven't been prepared for a commit.
• Changes Staged for Commit: Files ready to be included in your next commit.

Example:

On branch main
Your branch is up to date with 'origin/main'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   script.py

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	new_feature.js

2. git diff - Unveiling the Specifics:

git diff

This command reveals the exact differences between your current working copy and the last committed version.

Example:

--- a/script.py
+++ b/script.py
@@ -1,5 +1,5 @@
 def greet(name):
-    print(f"Hello, {name}!")
+    print(f"Greetings, {name}!")
 
 greet("Alice")

3. git log - A History of Changes:

git log

This command displays a timeline of commits, showcasing author, date, and commit messages.

Example:

commit 9848e20a68b9154136007a1482311eb734971d38 (HEAD -> main, origin/main)
Author: John Doe <[email protected]>
Date:   Fri Dec 9 14:39:00 2022 +0100

    Refactor: Update greeting message

commit 20a2781603e0a71e7768440d4139f3789d8d1c2e
Author: John Doe <[email protected]>
Date:   Fri Dec 9 14:21:00 2022 +0100

    feat: Add greeting function

Analyzing Changes: A Deeper Dive

• git diff --cached: This command reveals the changes you've staged, comparing them to the last commit.
• git diff <commit1> <commit2>: Compare two specific commits to see the changes between them.
• git diff <branch1> <branch2>: Compare changes between two branches.

Practical Example:

Imagine you're working on a new feature and want to see the changes you've made since starting work on it:

git checkout feature-branch # Switch to your feature branch
git diff origin/main # Compare your branch to the main branch

This will show you the changes you've made specifically in your feature branch compared to the main branch.

Further Exploration:

• GitHub: Utilize GitHub's "Compare" feature to visualize changes between commits or branches directly on the platform.
• GUI Tools: Git clients like GitKraken or Sourcetree offer visual representations of changes, making it easier to grasp the impact of your modifications.

Remember, mastering Git is a journey, and understanding how to see changes is a key step in that journey. The more you practice and explore, the more confident you'll become in navigating the intricacies of this powerful version control system.