fix(ci): open the traceability refresh PR when only merged PRs exist - #544
Draft
nbarbettini wants to merge 1 commit into
Draft
nbarbettini wants to merge 1 commit into
nbarbettini wants to merge 1 commit into
Conversation
`gh pr view <branch>` also resolves to closed/merged PRs, so once modelcontextprotocol#292 (head `traceability-refresh`) merged, every scheduled run found it and skipped `gh pr create`. Only skip creation when an open PR exists. Fixes modelcontextprotocol#543 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
commit: |
This branch has not been 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
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.
Fixes #543.
The "Open/update the rolling refresh PR" step guarded
gh pr createwithgh pr view "$branch", which also matches closed and merged PRs. Since #292 (headtraceability-refresh) merged on 2026-05-19, every weekly run has force-pushed the branch and then skipped creating the PR. As a result,src/seps/traceability.jsonon main is still missing SEPs 1932, 1933, 2640 and 2663.This changes the guard to count only open PRs for the branch:
Nothing else changes. The
run/proposepermission split is untouched, and this PR doesn't regeneratetraceability.json.After this merges, the next scheduled run (Monday 06:00 UTC) or a manual
workflow_dispatchshould open the refresh PR from the already-updatedtraceability-refreshbranch.Checked against the live repo: the new guard evaluates to "create" for
traceability-refreshtoday, and to "skip" for a branch that has an open PR.🤖 Generated with Claude Code