Conversation
…n page The comparison with gh-stack and the setup page disagreed on whether registering a stack with GitHub's stacking API is experimental: #12991 dropped the word from both, and #13065 restored it in setup.mdx only. The CLI still says so in its `--no-github-native` help ("experimental, and silently skipped where the API isn't available"), so the comparison page now says it too, in the same words as setup.mdx. No other page claims the registration is stable; the rest describe it without saying either way. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Change-Id: I2384d66def400163904ef274f938ac1518d6cc63
Contributor
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
🟢 Approval recommended
The focused documentation update is accurate, consistent, and introduces no unresolved issues.
Review effort: Balanced
Findings: None
What changed in this PR
Restores the experimental caveat for GitHub-native stack registration, aligning the comparison page with CLI documentation and setup guidance.
Changes:
- Clarifies that registration is experimental.
- Notes silent fallback when the API is unavailable.
| File | Description |
|---|---|
src/content/docs/stacks/compare/gh-stack.mdx |
Aligns comparison wording with the CLI and setup page. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Member
Author
|
I'll remove experimental from the CLI instead. |
This was referenced Oct 2, 2026
jd
added a commit
that referenced
this pull request
Oct 2, 2026
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
This branch had an error being deployed
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
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.
The comparison with gh-stack and the setup page disagreed on whether
registering a stack with GitHub's stacking API is experimental: #12991
dropped the word from both, and #13065 restored it in setup.mdx only. The
CLI still says so in its
--no-github-nativehelp ("experimental, andsilently skipped where the API isn't available"), so the comparison page now
says it too, in the same words as setup.mdx.
No other page claims the registration is stable; the rest describe it
without saying either way.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com