ci: grouping strategy: by owner/ecosystem for github actions - #603
Merged
Conversation
stefan-ctrl
approved these changes
Aug 18, 2026
stefan-ctrl
left a comment
stefan-ctrl
left a comment
Member
There was a problem hiding this comment.
LGMT. Grouping seems reasonableand solve some issues with #600 that stacks to many responsibilities for updates into one blob :)
Some Issues of #600
Needs to be updated at the same time
| Module | Old | New |
|---|---|---|
| github/codeql-action/init | 4.37.6 | 4.37.7 |
| github/codeql-action/analyze | 4.37.6 | 4.37.7 |
Broken #448
| Module | Old | New |
|---|---|---|
| oss-review-toolkit/ort-ci-github-action | 1.1.0 | 1.2.0 |
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
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.
New grouping strategy: by owner/ecosystem
Why this is better than grouping by update-type
The old minor-patch / major split created one giant PR with every action in the repo, causing merge conflicts and hard-to-review diffs. Grouping by owner means:
• Each PR is semantically coherent (all Docker actions, all CodeQL actions, etc.)
• Conflicts are contained within one owner's actions, not across all of them
• The CodeQL group in particular avoids the real-world footgun of init and analyze being on different versions