Do not run deployment job when syncing forks - #1053
Open
Kaliumhexacyanoferrat wants to merge 1 commit into
Open
Conversation
Kaliumhexacyanoferrat
marked this pull request as ready for review
July 26, 2026 14:30
MDA2AV
approved these changes
Jul 26, 2026
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.
When creating or updating a fork, the action
Deploy Sitewill be triggered onmainof that fork, which fails because the fork usually does not have GitHub pages enabled (which is a good thing as it would create tons of identical websites otherwise). This creates noise for contributors as they receive an e-mail about the failed workflow everytime they sync the fork.Example: https://github.com/Kaliumhexacyanoferrat/HttpArena/actions/runs/30205713564/job/89803305823
This change updates the workflow to run only on a non-forked repository.