Repository navigation
Updated Detect AI workflow use pull_request_target - #1050
Merged
Merged
Conversation
tomkralidis
approved these changes
Oct 22, 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.
Workflows triggered by Pull Requests from forks to the upstream repository don't have access to secrets for security reasons. However, workflows triggered by pull_request_target can access secrets. To make them secure, we need to put some safeguards in place by hardening the restrictions and making sure they never checkout or run the PR code. In this case we only access the PR url, to pass it as an argument to the classifier script.
Please checkout this pygeoapi issue on the same topic:
geopython/pygeoapi#2461
Reference:
https://docs.github.com/en/actions/reference/security/securely-using-pull_request_target