Add Migrate from Mergify page#50
Open
samgutentag wants to merge 3 commits into
Open
Conversation
Net-new page mapping Mergify constructs to Trunk equivalents: queue_rules + GH rulesets, required_status OR-clauses + aggregator actions, priority_rules + label-driven submit API, and per-rule conditional testing + impacted_targets API. Sourced from clustered customer Q&A (cluster_id mergify-migration-in-flight, verdict missing, 2 pairs from trunk-anchor active POC). Page sits as a top-level MQ sibling to migrating-from-github-merge-queue, matching the existing flat structure. Acknowledges the conditional-status-check ergonomic gap upfront rather than burying it — Phil's Slack thread to the trunk-anchor team was honest about the tradeoff, so the docs should be too. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Remove the bogus comparison Tip link (placeholder URL) and tighten the Getting help section to match the sibling migrating-from-github-merge-queue page's support email pattern. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Move the migration sequence to be the first section after the intro. Dissolve the "mental shift" section into a single sentence in the intro so the admission-vs-testing split lands before step 1 without a separate preamble section. Mapping Mergify constructs and Observability move below the sequence as reference appendices. Drop the optional "run both in parallel" step. Phil's actual advice in the trunk-anchor thread was straight cutover (turn off Mergify rules, configure GitHub rulesets, enable Trunk) — no parallel-running recommended. The sibling GH MQ migration page's parallel-run pattern works because GH MQ activates per branch protection setting, but Mergify and Trunk would both target the same PRs and conflict. Replaced with an Info callout: configure a repo to use only one merge queue tool at a time. Also tighten step 4 (Turn off Mergify): say "uninstall the Mergify GitHub App and remove or comment out .mergify.yml" rather than the vaguer "disable the Mergify app." Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
samgutentag
added
the
needs review
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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.
Summary
merge-queue/migrating-from-mergify.mdx(sibling tomigrating-from-github-merge-queue)docs.jsonnav entry added next to the existing GH MQ migration pageWhy
Sourced from customer feedback mining (cluster
mergify-migration-in-flight, verified asmissing— no Mergify migration page existed). Content drawn from real Q&A in trunk-anchor's active POC: Phil's Slack thread covered the rulesets-driven admission, the OR-clause aggregator workaround, and the observability story in enough detail to lift directly into the page. The conditional-status-check ergonomic gap is acknowledged upfront rather than buried.