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
Followup to master -> main conversion #112
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: cevich The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
LGTM |
ci is broken, I commented over in #110 about it. I think something changed in podman that broke the images call |
Oof, okay, I'll wait for that to merge then rebase this. Thanks for the reference. |
note: This PR is pretty safe to override-merge as well. It shouldn't affect/change any automation behaviors. More just like "future-proofing". |
lgtm to force merge |
I reran the test and it failed again. There might be an issue on the main branch. I'll try and look at it today
|
This needs a rebase to pass CI. CI should be good. I pulled this patch and rebased on main and the failure goes away |
Fix the intended destination branch referenced in Cirrus-CI configuration. Also update the `latest_podman.sh` script so it won't be sensitive to `containers/podman` converting master -> main at some future date. Signed-off-by: Chris Evich <cevich@redhat.com>
Changes merged into #114 |
Fix the intended destination branch referenced in Cirrus-CI
configuration.
Also update the
latest_podman.sh
script so it won't be sensitive tocontainers/podman
converting master -> main at some future date.Signed-off-by: Chris Evich cevich@redhat.com