Conversation
Merge Protections🔴 2 of 5 protections blocking · waiting on 👀 reviews
🔴 👀 Review RequirementsWaiting for
This rule is failing.
🔴 🔎 ReviewsWaiting for
This rule is failing.
Show 3 satisfied protections🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The fallback note incorrectly says registration is skipped silently despite the CLI reporting its status.
Review effort: Balanced
Findings: 1
Open (1)
What changed in this PR
Updates Stacks setup documentation to remove the experimental label from GitHub-native registration.
Changes:
- Removes the experimental caveat.
- Retains fallback behavior guidance.
| File | Description |
|---|---|
src/content/docs/stacks/setup.mdx |
Updates GitHub-native registration status and guidance. |
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Registering a stack with GitHub's stacking API is no longer experimental: `mergify stack push` does it by default, and the CLI is dropping the word from its own help text. The setup page still said "(experimental)" in the Git config table and "The CLI marks the registration itself as experimental" in the note below it. Both are gone. The note also said the CLI skips the registration "silently" where the API isn't available, which was never accurate: the push reports `not registered on GitHub` on that row and writes the `Depends-On:` markers back into the pull request descriptions, then succeeds as usual. The note now says that. The comparison with gh-stack already describes the registration without the caveat, and no other docs page calls it experimental. This replaces #13149, which went the other way and restored the caveat. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Change-Id: If9ad66bf39535464876f097312368352247fc9c4
e972cda to
48dd436
Compare
Revision history
|
|
Re-pushed: the note no longer says the registration is skipped "silently". Where the API is unavailable, the push reports https://github.com/Mergifyio/docs/compare/e972cda8b7c7a423aeb327e0c6d26f9a881ab0ce..48dd4367e55b |
Registering a stack with GitHub's stacking API is no longer experimental:
mergify stack pushdoes it by default, and the CLI is dropping the wordfrom its own help text. The setup page still said "(experimental)" in the
Git config table and "The CLI marks the registration itself as experimental"
in the note below it. Both are gone.
The note also said the CLI skips the registration "silently" where the API
isn't available, which was never accurate: the push reports
not registered on GitHubon that row and writes theDepends-On:markersback into the pull request descriptions, then succeeds as usual. The note
now says that.
The comparison with gh-stack already describes the registration without the
caveat, and no other docs page calls it experimental.
This replaces #13149, which went the other way and restored the caveat.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com