-
Notifications
You must be signed in to change notification settings - Fork 60.7k
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
More on how INPUT_<VARIABLE_NAME> works or doesn't #19883
More on how INPUT_<VARIABLE_NAME> works or doesn't #19883
Conversation
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 |
👋 @jsoref Thanks for opening a PR! I'll get this triaged for review ⚡ |
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.
Great change, thanks @jsoref!
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
This is a follow-up to #7693
Why:
actions/runner#665 (comment)
What's being changed (if available, include any code snippets, screenshots, or gifs):
Removing prose that hints that a
composite
action would getINPUT_
prefixed environment variables.Instead, just point to the top of the doc where I previously added text that seems to describe what's happening.
Before
After
Check off the following:
Writer impact (This section is for GitHub staff members only):