MQ: merge-queue
summary
A service that implements an automated merge-queue for GitHub pull requests is built and deployed: PRs are queued via GitHub comments trigger, each entry is rebased onto current master, required GitHub statuses are checked, TeamCity (the CI) is asked to rebuild the rebased snapshot and the PR is merged only if required checks pass; branches are deleted on success and conflicts or failing required checks generate explanatory comments. The team faces >100 PRs/week from ~40 people (≈200k files changed, ~15k lines added/week) and reports faster, safer merges and fewer main-branch breakages.
AI-written summary · about
chapters (5)
related talks
26mA State of Continuous Merge: The Secret to More Productive Dev Teams
22mKeeping builds green at scale
14mMerge Queue
42mThe solution of merge hell in monorepo
25mSpace-Age GitOps: The Rise of the Humble Pull Request
15mMinion: Agent-Ready Dev Platform Behind 11% of Merged PRs
43mDevOps 2.0 - Bigger, Badder with More Automation
58mFeature Branches And Toggles In A Post-GitHub World