A simple Git branch workflow for safer releases

Keep each branch focused

Start a short-lived branch for one change. Small branches are easier to review, test, and merge than a long-running collection of unrelated edits.

Use names that describe the task so it is easy to find the branch later.

A useful commit message says what changed and why. Make commits small enough that each one tells a coherent part of the story.

Before opening a pull request, read the diff yourself and remove temporary files or unrelated formatting changes.

Describe the user-visible result and how you checked it. Include screenshots for visual changes and call out any setup steps reviewers need.

After merging, confirm the deployed version and keep a simple path to revert a change if something breaks.

Start a short-lived branch for one change. Small branches are easier to review, test, and merge than a long-running collection of unrelated edits.

Use names that describe the task so it is easy to find the branch later.

A useful commit message says what changed and why. Make commits small enough that each one tells a coherent part of the story.

Before opening a pull request, read the diff yourself and remove temporary files or unrelated formatting changes.

Describe the user-visible result and how you checked it. Include screenshots for visual changes and call out any setup steps reviewers need.

After merging, confirm the deployed version and keep a simple path to revert a change if something breaks.