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
workflows: issue_comment
triggers refactoring
#17419
Conversation
de436c8
to
f523e99
Compare
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.
LGTM
We also need to add docs, but that can be in a follow-up PR.
Too late, I was already doing it :D |
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.
One concern below, the other is a nit. Also, where was this tested?
f8baa22
to
e44285b
Compare
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.
@nbusseneau Did you validate this with a test commit already?
e44285b
to
cf56912
Compare
Ensure all checks use a consistent format. Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
For now keep the previous and new triggers as a transition phase. Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
cf56912
to
64b4617
Compare
This will avoid triggering both regular and 1.10 CI when commenting `/test-backport-1.10` on a backport PR, while still allowing additional comments or newlines after the initial test trigger phrase. Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
- `test-me-please` replaced with `/test`. - `build-me-please` replace with `/build`. - Other triggers as-is but prefixed with `/`. - Unified race detection trigger phrases with the rest of the document: singular race detection jobs will expose their unique trigger phrases directly from the PR checks. Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
64b4617
to
3d0bba0
Compare
I looked at the PR history and was like "hmmm, no I did not, why didn't I?" 🤔 So I added a I am opening a separate PR for testing. |
e501d51
to
3d0bba0
Compare
Anybody knows why https://github.com/cilium/cilium/actions/runs/1270095584 is failing? I suppose it is due to this:
Do we not allow empty commit descriptions anymore? |
All tests in #17465 successfully triggered, however please note that the PR tests the |
cc @qmonnet |
Reviews are in and required tests are passing. Marking ready to merge. |
No. |
IIRC, the conclusion of that discussion was that empty commits are sometimes useful, as illustrated here. I think we should revert. |
Please review per commit :)