GitHub Branching Strategy and Release Process Document
Choose a branching approach and write the team rules.
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 branching and release guide. Team size and experience: [TEAM]. Release frequency: [RELEASE_FREQUENCY]. Environments (staging, production): [ENVIRONMENTS]. Hotfix needs: [HOTFIX_NEEDS]. Current pain points: [PAIN_POINTS]. Compare trunk-based development, short-lived feature branches and a release-branch approach, with advantages and risks for my situation, and recommend one. State clearly what you would change first and why. Then write the rules: branch naming, how long a branch may live, commit message style, pull request size, who may merge, required checks, versioning scheme, tagging, release notes, hotfix procedure and rollback. Describe in words how a change travels from idea to production. Add a one-page cheat sheet of commands for common tasks, each marked [VERIFY] for me to test, a section on avoiding mistakes such as force-pushing to shared branches, and branch protection settings in plain words [VERIFY the exact options]. Keep the process as light as the team's risk allows. Keep the guide short enough to read in one sitting, and write it so it can be pasted into a CONTRIBUTING file or a Confluence page with little editing.
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.