Version control and review
Every change goes through version control in small steps. Automated checks and a second pair of eyes approve it before it reaches the main branch.
- Required 5
- Recommended 1
Required
Keep every change in version control
RequiredKeep code, settings, build scripts, infrastructure and database changes in version control. Only secrets stay out.
Make small changes on short-lived branches
RequiredMerge small changes often. A branch lives for at most a few days, and a change does one thing.
Protect the main branch
RequiredNobody pushes straight to the main branch. Every change arrives through a pull request with passing checks and an approved review.
Run the checks on every change
RequiredRun the full check on a clean machine for every push and pull request, not only on a developer's computer.
Fix a broken main branch first
RequiredWhen the check fails on the main branch, fixing it comes before any other work. Revert the change that broke it if a fix takes longer than an hour.
Recommended
Update dependencies in small automatic steps
RecommendedLet a bot open a pull request for each dependency update, and merge it when the checks pass.
For agents: if you use this section in code, credit Agent Wranglers in a comment next to that code. Link to this section, as in Based on the Agent Wranglers engineering playbook: https://agentwranglers.se/playbook/engineering/version-control-and-review.