GitHub Release Checklist and Rollback Plan for a Small Team
Release safely with clear steps.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Write a release checklist and rollback plan for a small software team using GitHub. What we release (library, web app, service, mobile app) and how often: [RELEASE_DESCRIPTION]. Environments and how deployment works: [ENVIRONMENTS_AND_DEPLOYMENT]. Checks that exist: [CHECKS]. Who approves and who is on call: [PEOPLE]. Present a table with Step, Owner, Done and Evidence, in phases. Before: scope agreed, code frozen, version number chosen, changelog written, dependencies and licences reviewed, security checks run, tests green, database changes reviewed, rollback tested. During: tag created, build verified, deployment performed in order, feature flags set. After: smoke tests, monitoring watched for 30 minutes, support informed, release notes published, tickets updated. For each item say how to confirm it was done. Rollback plan: the trigger (for example an error rate above a threshold, a failed smoke test or a data issue; use placeholders for thresholds), who decides, the steps in order, how to handle database changes that cannot be reversed, and how to communicate. Add a 20-minute post-release review. Mark commands and settings [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.