Skip to content

ci(mergify): recognise subtree PRs by the org convention - #41

Merged
systemfsoftware-bot merged 1 commit into
mainfrom
chore/subtree-queue-readme-form
Nov 13, 2026
Merged

systemfsoftware-bot merged 1 commit into
mainfrom
chore/subtree-queue-readme-form

Conversation

@systemfsoftware-bot

Copy link
Copy Markdown
Contributor

Brings the subtree queue in .mergify.yml to the form in the systemfsoftware/.github README:

  • one condition requires a single commit carrying both git-subtree-dir and git-subtree-split: <40 hex>, where before the two trailers could come from different commits;
  • -linear-history requires the merge commit a git subtree add or git subtree pull --squash writes, so a rebased or squashed subtree PR matches no queue instead of being merged as if it were a subtree.

The queue's checks and the default queue's conditions are unchanged.

The subtree queue now requires one commit carrying both git-subtree
trailers and a non-linear history, as the systemfsoftware/.github README
describes, so a rebased or squashed subtree PR matches no queue.
@systemfsoftware-bot
systemfsoftware-bot merged commit 4752f9f into main Nov 13, 2026
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