Repository navigation
feat: add grouped plugin update PR strategy - #15
Conversation
|
ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing |
gabemontero
left a comment
gabemontero
left a comment
There was a problem hiding this comment.
approve but one minor question in line
|
|
||
| Create one PR for an exact frontend/backend package pair, such as `pluginabc` and `pluginabc-backend`, when both have updates in the same run and use the same tag prefix. Each package keeps its own target version; the versions can differ. Packages without a matching update get individual PRs. | ||
|
|
||
| ```yaml |
There was a problem hiding this comment.
so from what I can tell in the code grouping is just done by default
not following what this chunk of yaml has to do with the grouping ...I'm not connecting the dots between this yaml and the text that precedes and follows it
can you elaborate ? Or was this included incorrectly?
There was a problem hiding this comment.
It's a snippet of the update-pr-strategy when consuming as a GH action, you can see our current one in the gitops repo here: https://github.com/redhat-ai-dev/ai-rolling-demo-gitops/blob/main/.github/workflows/plugins-updater.yaml
Co-authored-by: Gabe Montero <gmontero@redhat.com>
2 participants
What does this PR do?
groupedfunctionality to the updater, which can be used if we want to combine certain plugins into a single PR to reduce CI runs and keep logical changes togetherWhich issue(s) does this PR fix
How to test changes / Special notes to the reviewer