Prevent PR builds from running on forks #8993
Merged
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.
An issue was raised in Spring Session (spring-projects/spring-session#1678) detailing how builds were running on forked versions of the repo. I fixed the issue in #8698, this PR adds similar logic to the Spring Security repo to ensure builds don't run on forks.
More detail:
Github Actions doesn't currently have an elegant way to prevent builds on forks. Following the suggestion outlined here, I added checks for each job to ensure it only runs on spring-projects/spring-session.
I opened a PR on my forked version and confirmed that no builds steps ran. See https://github.com/elliedori/spring-security/pull/6/checks?check_run_id=1062839692 for more.