Stage 10 · Lesson 3 of 5
CI and one pull request per slice
Set up (CI) early: automated checks that run on every , such as tests, type checking, linting and your security scanners, using or similar. Make them required before merging. CI checks every change the same way, whoever or whatever wrote it, and catches what a rushed review misses.
Then open one small pull request per slice, even on a solo project, with a description of what changed, how it was tested and what the agent did versus what you did. Review it yourself the next morning with fresh eyes. The history this leaves shows how you work, which is what someone reading your portfolio looks at.
Common trapone giant "initial " containing the whole project, which hides every decision you made.
A question to check yourself, an AI practice session and 2 cheat sheet entries come when you add the roadmap to your account. Add it
Resources for this stage
Start with· follow one of these
- GitHub repoFreeGitHub Skills: Getting Started with GitHub Copilot
GitHub · Beginner
Its last step uses Copilot to summarise and review pull requests, as you will in this project
- GuideFreeHow to Write a Git Commit Message
Chris Beams · Beginner
Seven rules for commit messages that make your project history readable