<style> .box { display: Inline-block; text-align: center; padding: 15px; background-color: #23EB9A; border-radius: 10px; align-items: Center; display: flex; justify-content: center; } </style>

Git Fundamentals and Commands Skills Application

---

Access and Credentials

Item	Detail
User	+++@lab.VirtualMachine(desktop1).Username+++
Password	+++@lab.VirtualMachine(desktop1).Password+++

---

Challenge Tasks

Task 1: Git Repository Setup and Configuration

Initialize a new Git repository and configure it with proper user settings and understand the basic Git workflow.

Requirements:

1. Create a new directory called git-fundamentals-project in your home directory
2. Navigate into the directory and initialize a new Git repository
3. Configure Git with your name and email address (use test values)
4. Create a .gitignore file that ignores common temporary files (*.tmp, *.log, .DS_Store)
5. Create an initial README.md file with a project description
6. Stage and commit the initial files with a descriptive commit message
7. Check the repository status and commit history
8. Document all commands used in git-setup-log.txt

Task 2: Working with Git States and Basic Commands

Demonstrate understanding of Git's three states (working directory, staging area, repository) through practical file operations.

Requirements:

1. Create three new files: main.py, utils.py, and config.json
2. Add some content to each file
3. Use git status to check the current state
4. Add only main.py to the staging area
5. Check status again to see the difference
6. Modify main.py after staging it
7. Use git diff to see the differences between working directory and staging area
8. Use git diff --cached to see differences between staging area and repository
9. Stage all files and commit them with a meaningful message
10. Document the different states and commands in git-states-explanation.txt

Task 3: Git History and Log Management

Explore Git's history features and understand how to navigate and analyze commit history.

Requirements:

1. Make at least 3 more commits by modifying different files
2. Each commit should have a clear, descriptive message
3. Use git log to view the commit history
4. Use git log --oneline to see a condensed history
5. Use git log --graph --oneline to see a graphical representation
6. Use git show <commit-hash> to examine a specific commit
7. Save the complete log output to commit-history.txt
8. Create a file called git-log-analysis.txt explaining what each log command shows
9. Use git log --author="YourName" to filter commits by author
10. Document your findings about different log formats and options

Task 4: Basic Branching and Repository Management

Create and work with Git branches to understand non-linear development workflows.

Requirements:

1. Create a new branch called feature-development
2. Switch to the new branch and verify you're on it
3. Create a new file called feature.py and add some content
4. Commit the new file on the feature branch
5. Switch back to the main branch and verify the file doesn't exist there
6. Create another branch called bugfix from main
7. Switch to bugfix branch and modify an existing file
8. Commit the changes on the bugfix branch
9. Switch back to main and merge the bugfix branch
10. List all branches and show which branch you're currently on
11. Document the branching workflow in branching-workflow.txt
12. Create a summary of all Git commands learned in git-commands-summary.txt

Task 5: Git Best Practices and Workflow

Demonstrate understanding of Git best practices and create a complete project workflow.

Requirements:

1. Create a development branch for ongoing work
2. Make several commits on the development branch with good commit messages
3. Use git commit --amend to modify the last commit message
4. Create a docs folder with documentation files
5. Use git add . and git add -A to understand the difference
6. Practice using git reset to unstage files (without losing changes)
7. Use git checkout to discard changes in working directory
8. Create a comprehensive git-workflow-guide.txt that explains:
   • When to use different Git commands
   • Best practices for commit messages
   • When and how to use branches
   • Common Git workflows
9. Demonstrate understanding by creating a clean commit history
10. Save final repository state and verify everything is properly committed

@lab.Activity(CFU2)