Draft
Conversation
inknos
force-pushed
the
automate-releases
branch
from
1ff6444 to
441f6d6
Compare
inknos
commented
Feb 5, 2026
Comment on lines
+5
to
+6
| url: https://github.com/containers/podman-py | ||
| ref: "v5.7.0" |
Contributor
Author
There was a problem hiding this comment.
adding a comment for reviewers and myself of the future
this is needed from Fedora side to pull tests and run gating in fedora PRs
https://src.fedoraproject.org/rpms/python-podman/pull-request/57#request_diff
This is a first step that makes the foundations for future work. Ideally we'd like to create this automatically when podman publishes a release. Signed-off-by: Nicola Sella <nsella@redhat.com>
inknos
force-pushed
the
automate-releases
branch
from
441f6d6 to
b10faac
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is a first step that makes the foundations for future work. Ideally we'd like to create this automatically when podman publishes a release.
At this state, ideally, the workflow will be done in 3 manual steps.
This is just an idea. Input is greatly appreciated.