Specify valid conditions for authorized-request label application#522
Merged
komish merged 1 commit intoJun 2, 2026
Merged
Conversation
The authorized-request label would be applied to PRs in cases where the chart-verifier job would not complete due to some transient error. Actual user verification is delegated to a script, but we can also prevent this label from being applied by being more specific in what job outcomes matter to us Signed-off-by: Jose R. Gonzalez <komish@flutes.dev>
This was referenced Jun 2, 2026
This was referenced Jun 2, 2026
This was referenced Jun 2, 2026
Contributor
|
If I understand correctly, /lgtm |
mgoerens
approved these changes
Jun 2, 2026
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
2 participants
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.
The authorized-request label would be applied to PRs in cases where the chart-verifier job would not complete due to some transient error. Actual user verification is delegated to a script, but we can also prevent this label from being applied by being more specific in what job outcomes matter to us (done here by ensuring that the outcome is either success or failure, and not allowing an empty value.