Module
Module 6 of 6Lesson 3 of 3~20 min

Final workshop: ship an improvement end to end

Lesson 3 of the module "Coding agent, releases and end-to-end delivery" in the course "Git for PMs: ship as a team without putting production at risk".

Take this lesson: your first course is freeSee the full syllabus

Lesson objective

By the end of this workshop, you will have shipped a small improvement through a pull request in a practice repository with CI and previews, meeting a definition of "ready to merge" and keeping evidence of every step.

Where it fits

Coding agent, releases and end-to-end delivery

How do I bring an AI agent into this workflow, mark a release and ship my first improvement?

Lessons in this module

  1. Put an AI coding agent to work in a team repository
  2. Tags, versions and release notes
  3. Final workshop: ship an improvement end to end (this lesson)

What you will learn in the course

This lesson is part of the course Git for PMs: ship as a team without putting production at risk

  • Read an existing repository and its pipeline (README, CONTRIBUTING, CODEOWNERS, CI workflows, environments) to know who reviews what, what gets checked and what goes to production, and when.
  • Work on a short-lived branch with everyday Git commands (or their GitHub equivalents), small commits named by convention, and stay in sync with main.
  • Open a small, well-described pull request, get the right review, pass the required checks, validate the preview and choose the merge method.
  • Resolve a simple merge conflict calmly, on the command line or in GitHub, and know when to ask for help.
  • Assess a repository's safety nets (branch protection, required checks, mandatory review, feature flags, staging, progressive rollout) and propose the missing ones.
  • Choose the right way to undo a change (restore, revert, reset, deployment rollback) depending on whether it is local, pushed, merged or already in production.
  • Keep an AI coding agent under control in a team repository (dedicated branch, written rules, protected secrets, proof of verification, human review before merge).
  • Tie merged changes to a release (tag, semantic versioning, changelog) and write release notes that help users.

Related courses