refactor: create the answers.md

This commit is contained in:
Bjarke Sporring
2026-01-05 12:21:30 +01:00
parent ceb5bd8031
commit e1b8d8418a
3 changed files with 70 additions and 23 deletions

View File

@@ -23,27 +23,23 @@ This will create a `challenge/` directory with a Git repository that already has
### Your Task
You'll explore an existing Git repository that contains multiple commits. Your goal is to use Git commands to discover information about the repository's history and answer the following questions:
You'll explore an existing Git repository that contains multiple commits. Your goal is to use Git commands to discover information about the repository's history.
1. **How many commits are in the repository?**
2. **What was the commit message for the third commit?** (counting from the first/oldest commit)
3. **Which file was modified in the "Fix authentication bug" commit?**
4. **What changes were made to app.py between the first and last commits?** (briefly describe)
Create a file called `answers.txt` in the challenge directory with your answers. You can format your answers however you like, as long as the information is there.
The setup script will create an `answers.md` file in the challenge directory with questions for you to answer. Fill in your answers directly in that file.
**Suggested Approach:**
1. Navigate to the challenge directory: `cd challenge`
2. View the commit history: `git log`
3. Try different log formats: `git log --oneline`, `git log --stat`
4. View specific commits: `git show <commit-hash>`
5. Compare commits: `git diff <commit1> <commit2>`
6. Create `answers.txt` with your findings
2. Open `answers.md` to see the questions
3. View the commit history: `git log`
4. Try different log formats: `git log --oneline`, `git log --stat`
5. View specific commits: `git show <commit-hash>`
6. Compare commits: `git diff <commit1> <commit2>`
7. Fill in your answers in `answers.md`
> **Important Notes:**
> - You can use any Git commands you like to explore the repository
> - The format of your answers is flexible - just make sure the information is clear
> - Fill in your answers directly in the `answers.md` file (there are placeholder sections for each answer)
> - Try different `git log` options to see which format you prefer
> - Commit hashes can be referenced by their full hash or just the first 7 characters
@@ -69,7 +65,7 @@ git diff <commit> # Compare commit with current working directory
## Verification
Once you've created your `answers.txt` file, verify your solution:
Once you've filled in your answers in `answers.md`, verify your solution:
```powershell
.\verify.ps1