-
Notifications
You must be signed in to change notification settings - Fork 61.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
Specify allowed contexts in jobs.<job_id>.services.<service_id>.image #33747
Conversation
Documentation does not mention if and which context variable can be used in `jobs.<job_id>.services.<service_id>.image`. From my tests a subset of contexts can be used and those are: `github`, `matrix`, `strategy`, `needs`, `vars` and inputs. Unfortunately, using `env` context is not possible. Not sure why but specifying allowed contexs in docs would be helpful when writing workflows. I've also changed conditional service creation example because it contained invalid example that was using `options` context which does not exist.
Automatically generated comment ℹ️This comment is automatically generated and will be overwritten every time changes are committed to this branch. The table contains an overview of files in the Content directory changesYou may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
fpt: Free, Pro, Team |
@piotrekkr Thanks so much for opening a PR! I'll get this triaged for review ✨ |
content/actions/using-workflows/workflow-syntax-for-github-actions.md
Outdated
Show resolved
Hide resolved
@piotrekkr - Thanks for raising this PR. I've asked the development team to confirm your changes before we go ahead and merge this. |
…ions.md Co-authored-by: hubwriter <hubwriter@github.com>
Closing this pull request because there is a list of available contexts in each configuration sections here. |
Why:
Documentation does not mention if and which context variable can be used in
jobs.<job_id>.services.<service_id>.image
. From my tests a subset of contexts can be used and those are:github
,matrix
,strategy
,needs
,vars
andinputs
.Unfortunately, using
env
context is not possible. Not sure why that is. Anyhow, specifying allowed contexts in docs would be helpful when writing workflows.I've also changed conditional service creation example because it contained invalid example that was using
options
context which does not exist.What's being changed (if available, include any code snippets, screenshots, or gifs):
Added a note about allowed contexts and fixed example conditional service creation.
Check off the following:
I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).
data
directory.For content changes, I have completed the self-review checklist.