Repository navigation
ci: run only on pull requests targeting main - #26
Merged
Merged
Conversation
Push to main no longer triggers CI, and PRs into other branches are skipped. Every change reaching main still passes through a PR, so the check runs once there instead of again after merge.
Merged
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.
What
Narrow the CI trigger in
.github/workflows/ci.yml:mainno longer triggers CI.mainare skipped.npm run checkon Node 20 and 22, then thedist/drift check.Why
Every change reaching
maingoes through a PR, so the check runs there once instead of again after merge.Note
With the push trigger gone, nothing re-runs on
mainafter merge. Branch protection onmainthat requires thecheckjobs to pass keeps that guarantee.