Repository navigation
ci: run on pull requests from branches of this repository - #46
Merged
Merged
Conversation
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 runs on every pull request from a branch of this repository, not only on pull requests that
rubasopens.Before: the
testjob inci.ymlhasProblem
rubas-agent[bot], so the job skips on them. deps: audit with mix hex.audit, bump mint and lazy_html #45 shows one skipped job and no test run.OTP ${{ matrix.otp }} / Elixir ${{ matrix.elixir }}and never the real check name.After
A pull request from a fork still skips the job. Only accounts that can push to this repository get CI, which keeps what the old rule protected.
Details
pull_requestevent comes from the pull request, so this PR runs its own CI with the new rule.mix hex.audit) waits for this PR. ci: run on pull requests from branches of this repository cloaked_req#76 makes the same change there.