-
Notifications
You must be signed in to change notification settings - Fork 389
fix(safe_jobs): hoist expression env vars into step env: block to prevent run-script guardrail failure
#32532
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
Changes from all commits
2885343
5253f26
96cca71
25c7ec1
7c95e37
8c171a3
12aeee7
3e610b3
f7c22cf
85dc43c
5e8b175
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice simplification — removing the intermediate
$GITHUB_OUTPUTwrite reduces one step and avoids the shell-injection risk that came with echoing arbitrary env var values. Usingrunner.tempexpression directly is cleaner.