Fix: prevent workflows from running on forks - #583
Merged
Conversation
MarlinMr
force-pushed
the
fix/workflows-fork-sync
branch
from
August 27, 2026 23:02
4674ce7 to
f4b34ce
Compare
murrant
approved these changes
Aug 28, 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
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.
Description:
This PR restricts the
buildandtestworkflows to only run on the upstream repository (librenms/docker).Changes:
if: github.repository == 'librenms/docker'condition to both workflow jobsWhy:
Forks were triggering build/test jobs unnecessarily, consuming CI resources. These workflows should only run on the upstream repo where the Docker images are actually published to Docker Hub.