Pin policies used by RHTAP Multi-CI #153
Merged
Conversation
This file contains 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
zregvart
approved these changes
Dec 2, 2024
With the imminent GA of RHTAP 1.3, let's pin this reference for stability. I pushed the branch to ec-policies just now on sha 158a9858c7be2250cd1ec8e7b80c7dca0d8ca01d . It means that changes from EC-1032 didn't get merged in time, but that's okay, we'll include them in future RHTAP releases. I considered introducing an RHTAP version number in the branch name, e.g. `release-v0.5-rhtap-1.3` but decided against it, though we may want to do somethinhg like that in future. Ref: https://issues.redhat.com/browse/EC-1029
simonbaird
force-pushed
the
pin-rhtap-multi-ci
branch
from
a4c4206 to
da5a991
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
With the imminent GA of RHTAP 1.3, let's pin this reference for stability. I pushed the branch to ec-policies just now on sha 158a9858c7be2250cd1ec8e7b80c7dca0d8ca01d .
It means that changes from EC-1032 didn't get merged in time, but that's okay, we'll include them in future RHTAP releases.
I considered introducing an RHTAP version number in the branch name, e.g.
release-v0.5-rhtap-1.3but decided against it, though we may want to do somethinhg like that in future.Ref: https://issues.redhat.com/browse/EC-1029