Repository navigation
Conversation
- Run tests and code quality on PRs into any base, not only main - Evaluate the Development merge check on stacked PRs - Refresh red merge checks on every open PR after a Development push
- Tests, code quality, and CodeQL run per stack (C# or Vue) only when the PR changes that stack or shared tooling - Pushes and scheduled runs still check everything
- CodeRabbit now requests changes on actionable issues and approves once its threads are resolved - New CodeRabbit Gate check passes only when its latest verdict is an approval
|
Warning Review limit reached
This review includes 7 billable files and costs up to $1.75.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Or wait 23 minutes for your next included review. View limit details
|
Bundle ReportBundle size has no change ✅ |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #392 +/- ##
=======================================
Coverage 49.45% 49.45%
=======================================
Files 1232 1232
Lines 62435 62435
Branches 8748 8748
=======================================
+ Hits 30876 30877 +1
+ Misses 30125 30124 -1
Partials 1434 1434
Flags with carried forward coverage won't be shown. Click here to find out more. |
|
@coderabbitai review |
Action not completed
|
Three CI improvements, one per commit.
Run PR checks on stacked PRs
Tests, code quality, and the Development merge check only ran for PRs targeting
main. A PR stacked on another feature branch, such as #383 on #385, got no tests or quality gates. Its merge check also stayed red after it landed in Development, because the refresh after a Development push listed only PRs intomain.Development.Skip C# and Vue checks a PR does not touch
A new composite action,
.github/actions/changed-stacks, diffs the PR against its base and reportscsharpandvueflags. Heavy jobs skip when their stack is untouched:web/,test/,Viper.sln*,Directory.Build.props,global.json,.config/VueApp/, ESLint/oxlint/stylelint configs,.env*package*.json,scripts/,.editorconfig, the workflow's own file, the action itselfPushes to
mainand the weekly CodeQL schedule still run everything. No status checks are required today, so skipped jobs can't block a merge. A job skipped byif:also counts as passing if checks become required later.CodeRabbit Gate check
.coderabbit.yaml:request_changes_workflow: true. CodeRabbit now requests changes when it finds actionable issues, and approves once its threads are resolved. A declined finding passes once its thread is resolved with a reply.CodeRabbit Gateworkflow: it passes only when CodeRabbit's latest verdict (approve, request changes, or dismissed) is an approval. It re-runs on every push and every review. Drafts and Dependabot PRs are skipped.Notes:
Test plan
tests.yml,code-quality.yml,codeql.yml, and the action, so every job should run here