Practice Checklist
Use this checklist for repeated practice. The same flow should be repeated several times with small changes.
Round 1 — README change
Section titled “Round 1 — README change”- Clone the practice repository.
- Switch to
main. - Pull the latest changes.
- Create a branch named
docs/add-my-name. - Add your name or initials to a practice section in
README.md. - Run
git status. - Stage the file.
- Commit with a clear message.
- Push the branch.
- Open a pull request.
- Ask someone to review it.
- Merge it after review.
- Switch back to
main. - Pull the merged change.
Round 2 — Add a notes file
Section titled “Round 2 — Add a notes file”- Create a new branch named
docs/add-practice-notes. - Add a small file named
practice-notes.md. - Write three things you learned about Git.
- Stage the new file.
- Commit the new file.
- Push the branch.
- Open a pull request.
- Update the PR after feedback.
- Merge the PR.
- Pull the latest
main.
Round 3 — Fix a typo
Section titled “Round 3 — Fix a typo”- Create a branch named
fix/readme-typo. - Fix one typo in any markdown file.
- Run
git status. - Stage the changed file.
- Commit the change.
- Push the branch.
- Open a pull request.
- Merge the PR.
- Pull the latest
main.
Reflection questions
Section titled “Reflection questions”- What command tells you what Git sees?
- What command saves a local checkpoint?
- What command sends your commits to GitHub?
- What command brings GitHub changes down to your computer?
- Why do we use branches?
- Why do we use pull requests?