Auto-merge release-notes PRs from release-monitor#133
Merged
Conversation
Release-notes PRs add upstream RELEASE_v*.md verbatim — no LLM step, so the human checkpoint was guarding zero hallucination risk while delaying KB ingestion (chunks.json) until someone clicked merge. Days the cron runs cleanly but a maintainer is offline = drift between the masthead version stat (live) and what Ask Atlas can cite. Calls enablePullRequestAutoMerge after pulls.create. Falls back to the prior manual-merge behavior if the mutation errors. 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
release-monitor.ymlopens a release-notes PR, immediately enable native GitHub auto-merge (enablePullRequestAutoMerge, methodMERGE).core.warning).allow_auto_mergewas just enabled to make the mutation valid.Why
RELEASE_v*.mdcopied verbatim (or the GitHub release body) — not LLM-generated — so the human checkpoint here was guarding zero hallucination risk.rebuild-chunks.ymlalready auto-fires onresearch/**push and bot-commits new chunks. So this closes the loop.Future-proofing
build-chunks.jsagainst the new file), native auto-merge respects required checks. With none today it merges immediately.Test plan
workflow_dispatchrelease-monitor.ymlmanually after a release lands)rebuild-chunks.ymlfires on the merge commit andchunks.jsonpicks up the new release tag🤖 Generated with Claude Code