chore(spec): auto-polish bar-horizontal#5860
Merged
Merged
Conversation
Add 'basic' tag to features dimension to indicate base variant Co-Authored-By: Claude <noreply@anthropic.com>
3 tasks
MarkusNeusinger
added a commit
that referenced
this pull request
May 7, 2026
## Summary - Auto-polish PRs (e.g. #5916, #5870, #5860) were sitting open with all required checks green because the polish prompt explicitly forbade auto-merge — they piled up waiting for a human to click merge. - Patch the polish prompt to call \`gh pr merge --auto --squash --delete-branch\` right after \`gh pr create\`. Auto-merge handles the strict required-status-check rule on \`main\` by updating the branch automatically when behind. - Update the \"What you must NOT do\" section accordingly (remove \"do not auto-merge\", keep the \`approved\` label restriction and the no-\`--admin\` rule). - Rename the workflow step from \"opens PR — no auto-merge\" to \"opens PR with auto-merge\" so log titles match behavior. If \`gh pr merge --auto\` fails for any reason it falls back to a warning — the PR is still open and can be merged manually. ## Test plan - [ ] Next \`daily-regen\` cycle produces a polish PR with auto-merge enabled (visible via \`gh pr view <num> --json autoMergeRequest\`). - [ ] After CI passes, the PR squash-merges into main without manual intervention. - [ ] If the polish step finds nothing (\`NOOP\`), no PR is created (existing behavior). Co-authored-by: Claude Opus 4.7 (1M context) <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.
Automated spec polish from
daily-regenpre-flight.Spec:
bar-horizontalWhat changed
basictag to features dimensionWhy
The
bar-horizontalspecification describes the fundamental, non-grouped, non-stacked horizontal bar chart variant. Per spec-tags-generator.md guidance, thebasictag is informative and indicates a base variant. This addition clarifies the spec's classification and aligns with similar specs (e.g., sankey-basic).Hard guarantees from the prompt
id,issue,createdunchangedupdatedbumped to 2026-05-07T07:10:05ZAwaiting human review. The skip-gate in
daily-regenwill prevent additional auto-polish PRs for this spec while this one is open.