chore(maintainers): Document merge-batch workflow

Add a short maintainer guide for merge:batch and link it from the
existing merge policy docs.

Lock in the source-validation CI fixes discovered during the
merge-batch end-to-end exercise so shallow checkout and missing
base-branch fetch regressions fail the workflow contract test.
This commit is contained in:
sickn33
2026-04-05 10:57:09 +02:00
parent 85cd5ef082
commit e598f069b2
4 changed files with 73 additions and 1 deletions

View File

@@ -237,7 +237,7 @@ We used this flow for PRs [#220](https://github.com/sickn33/antigravity-awesome-
**Maintainer shortcut for batched PRs:**
- Use `npm run merge:batch -- --prs 450,449,446,451` to automate the ordered maintainer flow for multiple PRs.
- Use `npm run merge:batch -- --prs 450,449,446,451` to automate the ordered maintainer flow for multiple PRs. See [docs/maintainers/merge-batch.md](../docs/maintainers/merge-batch.md) for the short usage guide.
- The script keeps the GitHub-only squash merge rule, handles fork-run approvals and stale PR metadata refresh, waits only on fresh required checks, retries `Base branch was modified`, and runs the mandatory post-merge `sync:contributors` follow-up on `main`.
- It is intentionally not a conflict resolver. If a PR is conflicting, stop and follow the manual conflict playbook.