-
Notifications
You must be signed in to change notification settings - Fork 1.2k
CI - check for the ci/no-release label first #7948
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
pavoljuhas
merged 1 commit into
quantumlib:main
from
pavoljuhas:ci-release-check-labels-first
Mar 11, 2026
+22
−13
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That
sedcommand concerns me due to its complexity and assumption about the format of the log message. The following may be more robust:pr_number=$(gh pr list --search "${{ github.sha }}" --state merged --json number --jq '.[0].number')There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack. I thought about that option, but I feel it is vulnerable to race condition. The push event that starts this workflow is emitted right after the PR merge to main, ie, after the state flip from OPEN to MERGED.
gh pr list --searchpresumably checks some database and I am not sure it is guaranteed to be up-to-date by the time of thepushevent. OTOH, the main head must exist in the working repo and for the past 4 years the commit subject line has ended in(#PR_NUMBER)(the first exception being #5196 which might have been a manual push).In the worst case, when
sedpattern does not match, thepr_numberis set to an empty string which is handled just as the default no-special-label case.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point about the potential race condition.