ci: use environment variables in GitHub Actions for improved security #9433
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 improves the security of the backport GitHub Actions workflow by using environment variables instead of direct context interpolation in shell commands.
Testing
Successfully tested in
aquasecurity/trivy-testrepository:Changes
${{ github.repository }},${{ github.actor }}) with built-in environment variables ($GITHUB_REPOSITORY,$GITHUB_ACTOR)Security Improvements
This change follows GitHub Actions security best practices by:
Checklist