ci: handle security workflows for fork pull requests - #800
Open
ANSHUL-REAL wants to merge 2 commits into
Open
Conversation
ANSHUL-REAL
force-pushed
the
ci/skip-snyk-on-fork-prs
branch
from
September 2, 2026 07:19
c2bab8a to
80b2d7e
Compare
ANSHUL-REAL
changed the title
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
1 participant
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.
This resolves two CI workflow problems:\n\n- Skip Snyk for external fork pull requests because GitHub withholds the repository-owned SNYK_TOKEN from those runs. Internal pull requests, pushes, merge queues, manual dispatches, and scheduled scans retain the Snyk check.\n- Remove the empty .github/workflows/semgrep.yml. GitHub registers it as an active workflow, then immediately fails it because it has no workflow definition or jobs.\n\nThe actual Gradle wrapper-validation workflow passes.