Merging and Deploying
From safe code to deployed product
8 lessons37 minPlus
Lesson 1 is free now. The rest comes with Plus.
What's inside
- Safe merge strategies
- Automated release artifacts
- Staging vs production deployment flows
What you'll gain
Ship AI-built features to production without the fear of what you might have missed.
- You'll merge code that's been reviewed, generate release artifacts like checklists and notes, and deploy to staging or production with a repeatable, safe process.
When to use it
- Deploying a feature to staging for QA
- Shipping to production with confidence
- Creating release notes and deployment artifacts
You'll reach for it: Every feature deployment
What you leave with
11
Prompts
Syllabus
8 lessons · 37 min1
Know What Production Needs
Reviewed code tells you the change is correct, not that production is ready for it. In this lesson we get an agent to read the diff and hand back the exact setup that change needs to run live.
5 minFree
2Block What Shouldn't Ship
The things that shouldn't ship are easy to leave in, a pasted API key, a forgotten dump, because none of them stop the code working. In this lesson we build a ship-gate skill that reads your staged diff and gives a straight pass or block before you commit.
6 min
3Get CI Without Writing YAML
Checks that only run when you remember aren't really checks. In this lesson you describe your project to an agent and get a working GitHub Actions pipeline that tests on every push and deploys on green, without writing any YAML by hand.
6 min
4Ship It Dark, Flip It Live
When merging and releasing are the same move, every launch is a big-bang one. In this lesson you put a finished feature behind a feature flag, ship it to main dark, and flip it on live when you're ready.
3 min
5Prove It Works in Production
A green build means the tests passed and it deployed, not that a real person can use the feature. In this lesson we build a qa-checklist skill that reads a change and gives you a short, focused list to check against the live app.
2 min
6Changelogs That Write Themselves
A changelog is the job that gets skipped every time you release. In this lesson you set up a GitHub Action that reads the commits since your last tag and writes a technical changelog into CHANGELOG.md for you.
3 min
7Release Notes for Real People
Your users don't care about a refactored controller, they care what changed for them. In this lesson you extend the release workflow to turn the same commits into a plain-English "what's new" and post it straight onto the GitHub release.
5 min
8Docs That Update Themselves
Docs drift because keeping them current is a separate job you have to remember. In this lesson you build a docs subagent that updates only the pages a change affects, wired to run on commit so they stay in sync on their own.
7 min
Access
It's part of Plus. Lesson 1 is free to watch for everyone, no account needed, and so is the brief above.
Every lesson of every course, the full notes, transcripts and prompts, and the Unlearn-built tools. Blog posts and the tools that are public on GitHub stay free for everyone.
It shows as Completed on your profile and counts toward its role. Finishing every step of a role earns the role certificate.
Yes. Team plans can assign this course, or a whole role, and follow progress in Team.
Next step
Next in Product Engineer
Debugging and Performance
Workflow · 9 lessons