Skip to content

Run CI once per change instead of twice - #51

Merged
MrTig-afk merged 1 commit into
mainfrom
chore/ci-single-trigger
Sep 2, 2026
Merged

Run CI once per change instead of twice#51
MrTig-afk merged 1 commit into
mainfrom
chore/ci-single-trigger

Conversation

@MrTig-afk

@MrTig-afk MrTig-afk commented Sep 2, 2026

Copy link
Copy Markdown
Owner

on: push: had no branch filter, so a PR branch matched both push and pull_request and ran the entire suite twice on every push. Visible as fail=2 on #47, #48 and #49: two identical backend runs, two failure emails each.

Limits the push trigger to main. PR branches now run once via pull_request, main runs once via push. Halves CI minutes and email volume, no loss of coverage.

Summary by CodeRabbit

  • Chores
    • Continuous integration workflows now run on pushes to the main branch. Pull request checks remain unchanged.

@vercel

vercel Bot commented Sep 2, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
mingle-hub Ready Ready Preview Sep 2, 2026 8:44am UTC

@coderabbitai

coderabbitai Bot commented Sep 2, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Team

Run ID: 68d5627e-8f0c-42ba-a12f-901a7c5f7bad

📥 Commits

Reviewing files that changed from the base of the PR and between 268ae22 and c7781a1.

📒 Files selected for processing (1)
  • .github/workflows/ci.yml

Included review availability: Your plan provides up to 8 included reviews per hour; 3 remain after this review.


📝 Walkthrough

Walkthrough

The CI workflow now triggers on pushes to main only. Pull request triggers remain unchanged.

Changes

CI trigger configuration

Layer / File(s) Summary
Restrict push-triggered CI runs
.github/workflows/ci.yml
The push trigger now applies only to the main branch. The pull_request trigger remains unchanged.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to c7781

This change limits CI push runs to main so pull requests run once instead of twice, reducing duplicate CI work and notifications without a demonstrated coverage regression; no actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes the main change: preventing duplicate CI runs so each change runs CI once. It is concise and specific.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/ci-single-trigger

Comment @coderabbitai help to get the list of available commands.

@MrTig-afk
MrTig-afk merged commit 96cb85c into main Sep 2, 2026
6 checks passed
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.

1 participant