docs: add branch protection setup script and stacking workflow guide#337
Merged
Blackgaurd merged 2 commits intoMay 15, 2026
Merged
Conversation
|
This was referenced May 15, 2026
Blackgaurd
force-pushed
the
chore/merge-queue-stack-action
branch
from
f21e329 to
f7ffff6
Compare
Blackgaurd
force-pushed
the
chore/merge-queue-tooling
branch
from
09f1ae8 to
c01fb8b
Compare
Blackgaurd
force-pushed
the
chore/merge-queue-tooling
branch
from
311e9fb to
8f94dcf
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
adds two things:
.github/scripts/setup-branch-protection.sh— one-shot script to apply branch protection viagh api. sets required status checks (backend-lint,backend-unit-tests,backend-integration-tests,frontend-precommit), 1 required approval, dismiss stale reviews, no force-push. prints colored instructions for the two manual UI steps (merge queue settings and allowing auto-merge) that the API cannot configure.dev-docs/stacking-workflow.md— developer guide covering the full stacking workflow: creating stacks, syncing, shipping via merge queue, resolving conflicts, and a command reference table. reflects the team's chosen workflow: every PR needs approval, auto-merge enabled via `gh pr merge --auto --rebase`, manual bottom-up queue submission.