Repository navigation
Run CI on pull requests so fork PRs get checks - #239
Merged
Merged
Conversation
Closed
Collaborator
Author
|
needed to run CI to merge #237 and in general to handle future PRs from forks |
merlerm
enabled auto-merge (squash)
October 7, 2026 13:08
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.
CI only triggers on
push, and a push to a fork runs in the fork, so PRs from forks (e.g. #237) never get the required checks and stay blocked.New triggers:
pull_request: every PR gets CI, whether its branch is in this repo or a fork. Checks run on the PR merged withmain.pushtomainonly:mainis checked after each merge, and a PR branch is not checked twice.workflow_dispatch: a "Run workflow" button on the Actions tab runs CI on any branch, e.g. one without a PR yet.Fork runs get a read-only token and no secrets, and
ci.ymldoes not use any secrets.