Build & submit taskBetaadvanced

Capstone: A Release, End to End

Ship one change the way strong teams do, using everything from the course: a feature branch and a pull request on GitHub with a rule on main, a squash merge, a signed release tag, a release built from that tag, a GitOps deployment to staging and production with Argo CD, and a rollback by revert. A local self-check verifies GitHub's side, the signature, the release and what Argo CD runs and has run, and writes your submission for instant, rubric-based feedback.

1.3 hrs

Est. time

Outcomes

Rubric criteria

60%

Pass score

What you'll learn

Skills you'll have real reps in after shipping this.

A release is a chain of evidence: pull request, squash commit, signed tag, release built from the tag, deployment commits, and the agent's history.

Each safeguard has a job: rules force review, squash keeps main readable, signatures prove origin, staging catches problems, reconciliation keeps the cluster honest.

Rolling back in GitOps is a revert, recorded like every other step.

The scenario

Bean There's winter special is ready to go online. The website's source lives on GitHub; its deployment configuration lives in a GitOps repository that Argo CD watches.

The release must follow the team's process from start to finish: reviewed in a pull request, merged without cluttering main, tagged with a signature, tested in staging, promoted to production, and, when the owner pulls the special from production for a day, rolled back cleanly.

Your role

You are the developer running the release. Your deliverable is cafe-site on GitHub with a squash-merged pull request and a pushed, signed v1.1.0 tag, and capstone-config with release v1.1.0 exported from that tag, deployed to staging, promoted to production from a branch and rolled back with a revert, all applied by Argo CD, plus notes on the trail and the safeguards.

Start the task to unlock the full brief

You'll get the step-by-step requirements, setup commands, the 4-criterion grading rubric, tips, and the ability to submit your solution for instant AI grading.

Free to start · submit when you're ready

Learning resources

GitHub Docs: About merge methods (squash and merge)

docs.github.com

GitHub Docs: About rulesets

docs.github.com

git tag documentation (signed tags)

git-scm.com

Argo CD documentation

argo-cd.readthedocs.io

A complete Git release workflow, from pull request to GitOps rollback

The capstone of Preporato's Git course runs one change through a professional release process from start to finish: a feature branch and a pull request on GitHub under a ruleset, a squash merge, a signed release tag, a release built byte for byte from that tag, a GitOps deployment to staging and production with Argo CD on a local Kubernetes cluster, and a rollback by revert. A local self-check verifies GitHub's side through Git itself (the merge button's commits and the pull request refs), the tag's signature, the release, and what Argo CD runs and has run, then writes your submission only when everything genuinely passes.

Frequently asked questions

How can a script check what I did on GitHub?

Through Git itself. GitHub records its merge button as the committer (GitHub <[email protected]>), titles a squash commit with the pull request number, and exposes every pull request's commits as refs/pull/N/head. check.sh fetches those and compares them.

Why can't I approve my own pull request?

GitHub doesn't let an author approve their own pull request. In this solo capstone, set the ruleset's required approvals to 0, review your own changes, and push a follow-up commit; on a team, a colleague's approval would be required.

Do I need a cloud account?

Only GitHub, which is free. The deployment runs on your own computer: kind runs Kubernetes inside Docker, with Argo CD and a practice Git server in the same cluster.