Skip to content

fix(ci): run Development merge check on stacked PRs - #391

Closed
rlorenzo wants to merge 1 commit into
mainfrom
fix/dev-merge-check-stacked-prs
Closed

rlorenzo wants to merge 1 commit into
mainfrom
fix/dev-merge-check-stacked-prs

Conversation

@rlorenzo

Copy link
Copy Markdown
Contributor

The advisory Development merge check only looked at PRs targeting main, in both places it runs:

Changes:

  • pull_request now runs for any base except Development (a PR into Development is never in Development before it merges).
  • The push refresh re-runs red checks on every open PR, whatever its base.

@coderabbitai

coderabbitai Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

  • Run on-demand review

This review includes 1 billable file and costs up to $0.25.

  • Ask an admin to make reviews automatic

Open in CodeRabbit

Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing.

Or wait 47 minutes for your next included review.

Check out review usage here.

View limit details

Limit details: You’ve used all 2 included reviews currently available. Your 55 included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour.

Learn how review limits work.

Review configuration:

Run configuration

  • Source mode: Auto
  • Repository: ucdavis/VIPER
  • Branch: main
  • File: .coderabbit.yaml
  • Commit: 0c3c822
  • Layers: Repository YAML
  • Review profile: ASSERTIVE
  • Plan: Essentials
  • Run ID: 7683a545-b02e-4149-bb8f-e14b40d45868
Commits

Reviewing files that changed from the base of the PR and between 0c3c822 and ba20329.

Files selected for processing: 1

  • .github/workflows/development-merge-check.yml
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

@codecov-commenter

Copy link
Copy Markdown

Bundle Report

Bundle size has no change ✅

- Evaluate PRs into any base except Development, not only main
- Refresh red checks on every open PR after a Development push
@rlorenzo
rlorenzo force-pushed the fix/dev-merge-check-stacked-prs branch from c744a9f to ba20329 Compare November 10, 2026 17:30
@codecov-commenter

codecov-commenter commented Nov 10, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 49.45%. Comparing base (0c3c822) to head (ba20329).
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #391      +/-   ##
==========================================
- Coverage   49.45%   49.45%   -0.01%     
==========================================
  Files        1232     1232              
  Lines       62435    62435              
  Branches     8748     8748              
==========================================
- Hits        30876    30875       -1     
  Misses      30125    30125              
- Partials     1434     1435       +1     
Flag Coverage Δ
backend 46.94% <ø> (ø)
frontend 67.44% <ø> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

@rlorenzo rlorenzo closed this Nov 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants