Repository navigation
ci: block upstream issue/PR refs in PR text - #71
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0163hpDCucArS53wRsiLQDw7
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
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.
Requested by Clankmaster · project thread
Before: a sync PR could list upstream commits with closing keywords and issue numbers, which GitHub shows on the upstream issue as a linked PR.
After: a new check fails any PR whose title, body or first-parent commit messages carry a closing keyword with a number, an owner/repo number reference, or a GitHub issue/pull URL outside prokrypt.
How:
.github/workflows/upstream-ref-check.ymlgreps those texts, with title and body passed through env vars.🤖 Generated with Claude Code
https://claude.ai/code/session_0163hpDCucArS53wRsiLQDw7
Generated by Claude Code