Prevent build-and-deploy workflow from running in forks - #11893
Open
MarkvanMents wants to merge 1 commit into
Open
Prevent build-and-deploy workflow from running in forks#11893MarkvanMents wants to merge 1 commit into
MarkvanMents wants to merge 1 commit into
Conversation
The push and pull_request triggers caused the workflow to run in forked repositories, wasting Actions minutes and potentially failing on missing secrets. Adding `if: github.event.repository.fork == false` to the build job ensures the workflow only runs in the main repository. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
2 participants
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.
Issue
The
build-and-deploy.ymlworkflow usespushandpull_requesttriggers scoped to thedevelopmentandproductionbranches. This caused the workflow to run in two unintended scenarios:developmentorproductionbranch triggers the workflow on pushes to those branches, consuming the fork's Actions minutes and failing when deployment secrets are absent.pull_requesttrigger fires the workflow in the main repo against the fork's code.Resolution
Added
if: github.event.repository.fork == falseto thebuildjob. Because thedeployjob depends onbuildvianeeds: build, it is automatically skipped wheneverbuildis skipped. The workflow now only runs in the main repository, for both push and pull request events.