-
Notifications
You must be signed in to change notification settings - Fork 213
chore: support konflux's ugly config... #4080
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
Conversation
1b47eed to
3d572c8
Compare
…o we can extract the package path (RHDHBUGS-2530) Assisted-by: Cursor Signed-off-by: Nick Boldt <nboldt@redhat.com>
3d572c8 to
383495e
Compare
|
|
/cherry-pick release-1.9 |
|
@nickboldt: once the present PR merges, I will cherry-pick it on top of DetailsIn 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. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Zaperex The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
The image is available at: |
|
hermeto validation passed with: |
|
@nickboldt: new pull request created: #4082 DetailsIn 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. |
|
merged, building in https://gitlab.cee.redhat.com/rhidp/rhdh/-/pipelines/14326738 to verify |



What does this PR do?
chore: support konflux's ugly config implementation for annotations so we can extract the package path (RHDHBUGS-2530)
assisted-by: cursor
Signed-off-by: Nick Boldt nboldt@redhat.com
Screenshot/screencast of this PR
N/A
What issues does this PR fix or reference?
(RHDHBUGS-2530)
How to test this PR?
PR Checklist
As the author of this Pull Request I made sure that:
Reviewers
Reviewers, please comment how you tested the PR when approving it.