CHANGELOG: the merge-queue click does not exist on a personal-account repo - #1720
Merged
Merged
Conversation
…xist on a personal-account repo Merge queues are organization-only (public repos on any plan, private on Enterprise Cloud); creating the recommended ruleset here returns 422 Invalid rule 'merge_queue'. The merge=union .gitattributes alternative is also out - GitHub's server-side PR merging ignores merge attributes (community discussion #9288). The merge_group wiring stays: inert, zero cost, live the day the repo ever moves to an organization. No separate CHANGELOG entry for this PR: it corrects an [Unreleased] entry in place - the change IS the changelog. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Corrects the #1716 [Unreleased] entry in place: merge queues are organization-only (public repos on any plan, private on Enterprise Cloud) - the GA announcement says so and the API confirms it here with 422 Invalid rule 'merge_queue'. Also records that .gitattributes merge=union is no alternative for the CHANGELOG trains (GitHub's server-side PR merge ignores merge attributes, community discussion #9288). The merge_group wiring stays: inert, zero cost, live if the repo ever moves to an organization.
No separate CHANGELOG entry: this PR corrects an [Unreleased] entry - the change IS the changelog. Incidentally this PR is also a live demo of the docs fast path on a real (non-throwaway) change.
🤖 Generated with Claude Code