Skip to content

feat(mergify): subtree PRs merge with a merge commit, never a squash (SYS-1246) - #3

Open
systemfsoftware-maker wants to merge 1 commit into
mainfrom
sys-1246-subtree-merge-commit
Open

systemfsoftware-maker wants to merge 1 commit into
mainfrom
sys-1246-subtree-merge-commit

Conversation

@systemfsoftware-maker

Copy link
Copy Markdown
Contributor

SYS-1246. Implements the org subtree-queue convention from systemfsoftware/.github#6 (ruling 9: subtree PRs merge with a merge commit, never a squash).\n\n## What changes\n\n- New queue (before ): , recognised from the commits themselves — a PR qualifies only when its commits carry the anchored + trailer pair that writes. Same check conditions as .\n- ** gains three exclusions**: trailer-bearing PRs, subtree-claim-titled PRs, and (this repo declares no subtree prefixes, so no path exclusion is needed). A subtree PR therefore can never squash, and a subtree claim without commit evidence matches no queue and cannot merge at all.\n- Pure subtree removals stay exempt; hand edits to vendored paths without trailers are blocked (that is the exact squash hazard SYS-1246 closes).\n- Recognition reads the commits; titles and labels never grant the merge path. Checks, approvals, and protections unchanged — nothing is loosened.\n\n## Validation\n\n- YAML parses (deno std yaml); the existing check/merge conditions are preserved verbatim (additions only).\n- The PR's own Mergify configuration check validates this file.\n- Org policy + audit: systemfsoftware/.github#6, tracked on SYS-1246.

…(SYS-1246)

Implements the org subtree-queue convention (systemfsoftware/.github#6):
a subtree queue keyed on the anchored git-subtree-dir/git-subtree-split
trailer pairs plus this repo's existing checks, merging with a merge
commit; the default queue excludes trailer-bearing PRs, claim-titled
subtree PRs, and hand edits under the declared subtree prefixes, so a
subtree PR can never squash and an unrecognised claim cannot merge at
all. Recognition reads the commits themselves; same checks, approvals
and protections as before.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant