ci: add ok-to-test label after Mergify rephrase
#5289
Merged
Conversation
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
nixpanic
added
ci/skip/e2e
mergify
bot
added
component/testing
Madhu-1
approved these changes
Apr 23, 2025
Mergify rephrased the status when a PR is the 1st in the queue. Instead of the "Queue: Embarked in merge train", the status is now reported as "Queue: Embarked in merge queue". Because the status did not match the rule in the configuration anymore, the `ok-to-test` label was not automatically added. Signed-off-by: Niels de Vos <[email protected]>
mergify
bot
force-pushed
the
mergify/ok-to-test
branch
from
7b81282 to
13620e2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Mergify rephrased the status when a PR is the 1st in the queue. Instead of the "Queue: Embarked in merge train", the status is now reported as "Queue: Embarked in merge queue".
Because the status did not match the rule in the configuration anymore, the
ok-to-testlabel was not automatically added.Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:
/retest ci/centos/<job-name>: retest the<job-name>after unrelatedfailure (please report the failure too!)