Skip to content
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

Add callout that some contexts aren't available for use in the jobs.<job_id>.if conditional #22436

Closed
1 task done
MarkIannucci opened this issue Dec 3, 2022 · 4 comments · Fixed by #22437
Closed
1 task done
Labels
content This issue or pull request belongs to the Docs Content team

Comments

@MarkIannucci
Copy link
Contributor

MarkIannucci commented Dec 3, 2022

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idif

What part(s) of the article would you like to see updated?

Please add a callout that certain contexts are not available for use in the jobs.<job_id>.if conditional. If you attempt to use them, you get an Unrecognized named-value: '<context>'. error.

Adding links to issues where people on the internet have learned about this the hard way:

Additional information

No response

@MarkIannucci MarkIannucci added the content This issue or pull request belongs to the Docs Content team label Dec 3, 2022
@welcome
Copy link

welcome bot commented Dec 3, 2022

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Dec 3, 2022
@cmwilson21
Copy link
Contributor

@MarkIannucci Thanks for opening an issue and linking it to your PR! ✨

@cmwilson21 cmwilson21 removed the triage Do not begin working on this issue until triaged by the team label Dec 5, 2022
@cognitiaclaeves
Copy link

cognitiaclaeves commented Jan 12, 2023

This is a necro-post, but I wanted to point out, in case anyone sees this later, that I don't think that PR #22437 addresses issue actions/runner#1189 at all -- to me, it is still completely vague as to whether or not one can refer to variables in env from the job context.

@cmwilson21
Copy link
Contributor

@cognitiaclaeves 👋 - Would you mind opening your concern as a new issue? That way I can triage it and make sure someone gets eyes on it for review 👀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants