-
Notifications
You must be signed in to change notification settings - Fork 24
build: revert infinite loop changes #141
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
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 Critical
Copilot Autofix
AI 3 months ago
To prevent potential code injection vulnerabilities with user-controlled input, the recommended GitHub Actions pattern is to pass the value into an environment variable and reference that variable from the shell. This involves two changes:
env:in the problematicrun:step, assigning something likePR_TITLE: ${{ github.event.pull_request.title }}.run:block, remove the direct variable assignment (PR_TITLE='...'), and simply use$PR_TITLEas needed.In this case, we:
PR_TITLE='${{ github.event.pull_request.title }}').env:under the step, definingPR_TITLE: ${{ github.event.pull_request.title }}.$PR_TITLEin therun:block already use the correct syntax.No new methods or imports are required.