SHA-1 hashing concept in Git - Mini Project: Build & Apply

SHA-1 Hashing Concept with Git

📖 Scenario: You are learning how Git uses SHA-1 hashes to identify commits uniquely. This helps Git track changes safely and efficiently.

🎯 Goal: You will create a simple text file, configure Git user info, commit the file, and then view the SHA-1 hash of the commit to understand how Git generates it.

📋 What You'll Learn

Create a file named example.txt with exact content Hello Git SHA-1

Configure Git user name as Test User and email as [e-mail]

Add and commit the file with message Initial commit

Display the SHA-1 hash of the latest commit using git log

💡 Why This Matters

🌍 Real World

Git uses SHA-1 hashes to track every change in a project safely. This helps developers collaborate without conflicts.

💼 Career

Understanding SHA-1 hashes in Git is essential for software developers and DevOps engineers to manage code versions and troubleshoot issues.

1

Create the file with exact content

Create a file named example.txt with the exact content Hello Git SHA-1.

Git

# Create the file example.txt with the exact content
# Your code here

Hint

Use the echo command to write text into a file.

2

Configure Git user name and email

Configure Git user name as Test User and email as [e-mail] using git config commands.

Git

echo "Hello Git SHA-1" > example.txt
# Configure Git user name and email below
# Your code here

Hint

Use git config user.name "Your Name" and git config user.email "[e-mail]".

3

Add and commit the file

Initialize a new Git repository using git init, add example.txt to Git staging area using git add example.txt and commit it with message Initial commit using git commit -m "Initial commit".

Git

echo "Hello Git SHA-1" > example.txt
git config user.name "Test User"
git config user.email "[e-mail]"
# Initialize the repository, add example.txt and commit with message "Initial commit"
# Your code here

Hint

Use git init to initialize a repository, git add to stage files and git commit -m "message" to commit.

4

Display the SHA-1 hash of the latest commit

Use git log -1 --format=%H to display the SHA-1 hash of the latest commit.

Git

echo "Hello Git SHA-1" > example.txt
git config user.name "Test User"
git config user.email "[e-mail]"
git init
git add example.txt
git commit -m "Initial commit"
# Display the SHA-1 hash of the latest commit
# Your code here

Hint

The command git log -1 --format=%H shows the full SHA-1 hash of the latest commit.

Practice

1. What does the SHA-1 hash in Git uniquely identify?

easy

A. A specific commit or file content

B. The username of the committer

C. The branch name

D. The date and time of the commit

Solution

1. Step 1: Understand SHA-1 purpose in Git

   SHA-1 generates a unique code based on the content of files or commits.

2. Step 2: Identify what SHA-1 represents

   It uniquely identifies the exact content or commit, not metadata like username or branch.

3. Final Answer:

   A specific commit or file content -> Option A

4. Quick Check:

   SHA-1 = unique content ID [OK]

Hint: SHA-1 hashes content, not user or branch info [OK]

Common Mistakes:

• Thinking SHA-1 identifies user info
• Confusing SHA-1 with branch names
• Assuming SHA-1 stores commit date

2. Which command correctly shows the SHA-1 hash of the latest commit in a Git repository?

easy

A. git log -1 --format=%H

B. git sha1sum HEAD

C. git show --hash

D. git commit --hash

Solution

1. Step 1: Recall Git command to show commit hash

   The command 'git log -1 --format=%H' prints the full SHA-1 hash of the latest commit.

2. Step 2: Check other options for correctness

   The other options are invalid or do not exist in Git syntax.

3. Final Answer:

   git log -1 --format=%H -> Option A

4. Quick Check:

   Correct Git syntax for latest commit SHA-1 is git log -1 --format=%H [OK]

Hint: Use git log with format %H for full commit hash [OK]

Common Mistakes:

• Using non-existent git commands
• Confusing commit message commands with hash commands
• Trying to use sha1sum directly on HEAD

3. Given the command git hash-object README.md, what is the expected output?

medium

A. An error because README.md is not a commit

B. The size of README.md in bytes

C. The last commit hash that modified README.md

D. The SHA-1 hash of the README.md file content

Solution

1. Step 1: Understand git hash-object command

   This command computes and outputs the SHA-1 hash of the file content given (README.md here).

2. Step 2: Verify output meaning

   It does not show file size, commit hashes, or errors for valid files.

3. Final Answer:

   The SHA-1 hash of the README.md file content -> Option D

4. Quick Check:

   git hash-object outputs file content SHA-1 [OK]

Hint: git hash-object hashes file content, not commits [OK]

Common Mistakes:

• Expecting commit hash instead of file hash
• Thinking it outputs file size
• Assuming it errors on normal files

4. You run git hash-object -w file.txt but get an error. What is the most likely cause?

medium

A. The -w option is not valid for git hash-object

B. The file.txt does not exist in the current directory

C. You need to commit before hashing

D. The file.txt is already tracked by Git

Solution

1. Step 1: Understand git hash-object -w usage

   The -w option writes the object to Git's object database; it requires the file to exist.

2. Step 2: Identify cause of error

   If file.txt does not exist, the command errors. Other options are incorrect because -w is valid, committing is not required, and tracking status doesn't cause this error.

3. Final Answer:

   The file.txt does not exist in the current directory -> Option B

4. Quick Check:

   Missing file causes git hash-object -w error [OK]

Hint: Check file existence before git hash-object -w [OK]

Common Mistakes:

• Thinking -w is invalid option
• Assuming commit is required before hashing
• Believing tracked files cause this error

5. You want to verify if a file's content matches a specific Git object SHA-1 hash. Which sequence of commands correctly helps you do this?

hard

A. Run git show SHA1_HASH and compare with file.txt content manually

B. Run git diff SHA1_HASH file.txt to see differences

C. Run git hash-object file.txt and compare output with the SHA-1 hash

D. Run git cat-file -p file.txt to get the hash

Solution

1. Step 1: Understand how to get file's SHA-1 hash

   Use 'git hash-object file.txt' to compute the SHA-1 hash of the file content.

2. Step 2: Compare computed hash with given SHA-1

   If the hashes match, the file content matches the Git object.

3. Final Answer:

   Run git hash-object file.txt and compare output with the SHA-1 hash -> Option C

4. Quick Check:

   Compare file hash with SHA-1 using git hash-object [OK]

Hint: Use git hash-object to get file hash for comparison [OK]

Common Mistakes:

• Using git show to compare file content directly
• Trying git diff with SHA-1 hash and file
• Using git cat-file incorrectly on files