-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[CI:DOCS] Packit: clarify secondary status in CI #25478
[CI:DOCS] Packit: clarify secondary status in CI #25478
Conversation
Signed-off-by: Lokesh Mandvekar <[email protected]>
69c4459
to
47079cd
Compare
[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore. |
Moving some CI info changes from #24369 for faster review and merge. @containers/podman-maintainers PTAL |
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. Thanks, I agree that this should make things much more clear.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lsm5, Luap99 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
LGTM, added No New Tests and restarted the failed job. |
/cherrypick v5.4 |
@lsm5: once the present PR merges, I will cherry-pick it on top of In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
BTW, most of these titles are gone as documented in https://github.com/containers/podman/blob/main/contrib/cirrus/CIModes.md cirrus is smart enough to skip test based on changes sources no user should have use these titles. |
/lgtm |
f10f326
into
containers:main
@lsm5: new pull request created: #25482 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Does this PR introduce a user-facing change?