Versyka
Posted on Nov 18
AI-assisted
Never auto-merge without these 4 rules. Your CI isn't enough. "Auto-merging dependency PRs is reckless" is the most common objection to dependency automation, and it's right if there are no rules. These are the four we wrote before shipping auto-merge for version bumps.
1. Only version bumps
The pull request changes version numbers in manifests and lockfiles and nothing else. The moment a PR touches code (a migration, a renamed function, a config change), it waits for a person. For us, that's the line between "this is routine" and "this needs judgement".
2. Every CI check passes
Not most, not only the required ones. All of them. And the rule people forget: no CI at all means no merge. A PR with zero checks passes "all checks green" in most scripts, which is how a bot merges untested code.
3. Never past a required review
If your branch protection asks for a reviewer, auto-merge waits for one. Automation should sit inside your rules, never around them.
4.…