Add DepGroupUpdate to c9k auto-issue-classes#11747
Conversation
Include grouped dependency updates (DepGroupUpdate) alongside major bumps when c9k auto-issues. Matches the v2.0.0 default class set minus FlakyTestRun, which is intentionally still excluded from issue creation (handled via auto-close-flaky).
|
This PR requires exactly 1 of the following labels: pr:standard, pr:important. Label descriptions:
@sylvainsf, please add the appropriate label to this PR before merging. |
Radius functional test overviewClick here to see the test run details
Test Status⌛ Building Radius and pushing container images for functional tests... |
There was a problem hiding this comment.
Pull request overview
Updates the CI failure reporting workflow to include grouped dependency updates in c9k’s auto-issue classification list, so failures caused by grouped dependency PRs can be tracked as their own root-cause issues.
Changes:
- Add
DepGroupUpdateto theauto-issue-classesinput for the c9k action in the scheduled failure report workflow.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #11747 +/- ##
==========================================
- Coverage 51.38% 51.37% -0.01%
==========================================
Files 699 699
Lines 44111 44111
==========================================
- Hits 22665 22663 -2
- Misses 19278 19279 +1
- Partials 2168 2169 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
What
Adds
DepGroupUpdatetoauto-issue-classesin .github/workflows/c9k-failure-report.yml so c9k will also auto-file issues for grouped dependency updates (e.g. dependabot grouped PRs), in addition to single major-version bumps.Why
Grouped dependency updates are a common source of CI breakage in this repo, and v2.0.0 of c9k classifies them as their own root-cause class (
DepGroupUpdate). Filing them gives us a per-cause issue instead of burying them in the rolling digest.Compatibility
FlakyTestRunis intentionally still excluded from this list, flaky groups are handled viaauto-close-flaky: trueand never get assigned to Copilot.Per the v2.0.0
action.yml, the default value isCodeChange,BrokenTestRun,DepMajorBump,DepGroupUpdate, so this brings the workflow in line with that default while keeping it explicit.