Repository navigation
ci: run on pull requests only, not on pushes to master - #11
Merged
Merged
Conversation
The branch ruleset only merges PRs that are up to date with master and passed build-and-test, so master receives exactly the code CI already checked; the post-merge run rebuilt it for nothing. CI now runs on pull requests and by hand. Releases still test before packaging. The README CI badge now reflects pull-request runs (it would otherwise stay frozen on the last master run). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Deploying dockz with
|
| Latest commit: |
53a0126
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://cae4f396.dockz.pages.dev |
| Branch Preview URL: | https://ci-pr-only.dockz.pages.dev |
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.
Summary
CI ran twice for every change: once on the PR, then again on master after merging. The second run only rebuilt code that had just passed.
ci.yml: triggers onpull_requestandworkflow_dispatchonly. The branch ruleset (requiredbuild-and-test, strict "up to date" policy, squash-only) already guarantees master gets exactly the tested code.?event=pull_requestso it tracks PR runs instead of freezing on the last master run.release.yml, onv*tags) still run the full test suite before packaging — unchanged.Test plan
pull_request,workflow_dispatch.?event=pull_requestresponds 200.ci.yml, so it builds once).🤖 Generated with Claude Code