-
Notifications
You must be signed in to change notification settings - Fork 17
dismiss Vale review and re-run after followup fixes #481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
Check failure
Code scanning / CodeQL
Code injection
Copilot Autofix
AI 9 days ago
To fix this, we must stop interpolating the untrusted branch name directly into the
run:script via${{ ... }}and instead pass it as an environment variable, then reference it using standard shell variable syntax. This prevents arbitrary code injection because the shell receives only the resolved environment variable value, and proper quoting can be applied.Concretely, in the step that currently contains:
we should:
env:section to this step that sets a safe environment variable, e.g.PR_BRANCH: ${{ steps.pr-info.outputs.branch }}.git pullinvocation to use the shell variable, properly quoted:git pull origin "$PR_BRANCH" 2>/dev/null || true.All other logic remains the same; we do not change how
branchis computed or stored, only how it is consumed in the shell. No new imports or external libraries are required; only YAML changes within.github/workflows/claude-doc-pr.ymlin the shown snippet.