-
Notifications
You must be signed in to change notification settings - Fork 58.2k
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
clarify that github.env
is not related to env
#32132
Comments
@jsoref Thank you for raising this issue! I'll get this triaged for review ✨ Our team will provide feedback regarding the best next steps for this issue - thanks for your patience! 💛 |
This comment was marked as spam.
This comment was marked as spam.
@jsoref Thanks again for submitting this issue!
After reviewing with the team, we found the PR you referenced confusing
Would you be able to write a workflow to test this? Your results would greatly help us determine next steps regarding this point ✨ |
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/actions/learn-github-actions/contexts#github-context
What part(s) of the article would you like to see updated?
The text for
github.env
says:Two things to add:
jobs.<*>.if
for the same reason thatenv
isn't -- see https://docs.github.com/en/actions/learn-github-actions/contexts#context-availabilityAdditional information
I ran into a PR where someone was trying to use
github.env.foo
in ajobs[*].if
to work around the fact thatenv
isn't available at this point.The text was updated successfully, but these errors were encountered: