Repository navigation
Clarify that vars context is unavailable in composite actions - #46312
imaloveabra wants to merge 1 commit into
Conversation
|
Please don't raise pull requests against an existing issue that another user has raised until it's been marked with a |
|
Thanks for submitting a PR to the GitHub Docs project! In order to review and merge PRs most efficiently, we require that all PRs grant maintainer edit access before we review them. For information on how to do this, see the documentation. |
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
Why:
Closes: #46232
The
varscontext is currently documented without mentioning that it's unavailable inside composite actions. This causes confusion as users expect${{ vars.MY_VAR }}to work.What's being changed:
Added a NOTE clarifying that
varsis not available in composite actions and showing the workaround to pass it as an input from the calling workflow.Check off the following: