-
Notifications
You must be signed in to change notification settings - Fork 856
.github: add downstream PR workflow for podman repo #6444
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
base: main
Are you sure you want to change the base?
Conversation
|
If the bot's not going to to do it, this needs text advising someone that they're expected to close the corresponding podman PR when their buildah PR is merged or closed. |
|
@mheon any concerns with running more CI tests? |
|
No, we definitely want this - reverse-dependency testing is something we've wanted for a long while |
|
@mheon I concur on the reverse-dependency testing, I'm just a little concerned about running out of CI resources without needing to pay more. We'll cross that bridge if/when we get there. |
|
@flouthoc I thought earlier today you said you had a change or two to do? I'm not seeing changes since the last comments, but the GitHub UI has been acting whacky this afternoon for me. Do you have more to do stiill? |
Automatically create PRs in podman when buildah PRs are opened to test compatibility and catch breaking changes early. This workflow is similar to: https://github.com/containers/container-libs/blob/main/.github/workflows/opendownstream-pr.yml Signed-off-by: flouthoc <[email protected]>
226e236 to
6f8d618
Compare
Modified the text in variable |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: curtiscrummie39, flouthoc 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 |
Automatically create PRs in podman when buildah PRs are opened to test compatibility and catch breaking changes early.
This workflow is similar to: https://github.com/containers/container-libs/blob/main/.github/workflows/opendownstream-pr.yml
What type of PR is this?
What this PR does / why we need it:
How to verify it
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?