ci(scrape): auto-merge the daily race-results PR#187
Merged
Conversation
The daily scraper has been creating a PR every day since Feb 27 without ever merging any of them — 77 stale PRs accumulated by 2026-05-14. Root cause: the workflow opens a PR and stops. Nothing schedules a merge, so each daily PR sits open until a human merges it. Combined with the repo-level allow_auto_merge being off (now enabled separately), this guaranteed the backlog. Add `gh pr merge --auto --squash --delete-branch` after pr-create so each day's PR squash-merges itself once CI is green, and its branch is cleaned up automatically. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
The daily scraper workflow creates a PR every morning but never schedules a merge — that's why 77 stale
auto/scrape-*PRs piled up between 2026-02-27 and 2026-05-14 before the backlog was cleared. Two things are required to fix it; this PR is the second:allow_auto_mergetotrueat the repo level (it wasfalse, which would silently reject any--autorequest even if the workflow asked).gh pr merge --auto --squash --delete-branchaftergh pr createin.github/workflows/scrape.yml, so each day's scraper PR squash-merges itself the moment CI goes green and cleans up its branch.CI is already green on every scraper run going back, so there's no expected blocker — the daily PR will simply land within minutes of being opened.
Test plan
gh pr createscrape.ymlworkflow (gh workflow run scrape.yml) and confirm:auto/scrape-YYYY-MM-DDbranch is deleted🤖 Generated with Claude Code