Outdated reusable workflow documentation regarding output behavior
Code of Conduct
- [x] I have read and agree to the GitHub Docs project's Code of Conduct
What article on docs.github.com is affected?
The documentation in the "reusing-workflow-configurations.md" section includes information that is now outdated based on current GitHub Actions functionality. https://github.com/github/docs/blob/main/content/actions/concepts/workflows-and-actions/reusing-workflow-configurations.md
Current text: "You can't add steps to a job after calling a reused workflow, so you can't use GITHUB_ENV to pass values to subsequent job steps in the caller workflow."
What part(s) of the article would you like to see updated?
Why this is outdated: GitHub Actions now supports defining and using outputs from reusable workflows. These outputs can be consumed in subsequent jobs in the caller workflow, even though additional steps cannot be added after invoking a reusable workflow within the same job. This change allows reusable workflows to pass values forward in a workflow, and the existing documentation does not reflect this behavior.
Suggested updated text: "You can't add steps to a job after calling a reused workflow, but reusable workflows now support outputs that can be referenced in subsequent jobs in the caller workflow."
Impact: Updating this wording will help prevent confusion for users relying on outdated guidance and bring the documentation in line with current reusable workflow capabilities.
If approved, I would be happy to submit a pull request to update this section.
Additional information
No response
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.
@SasiSriram Thanks for opening an issue and PR! I'll take this to the Actions team and see what they think.
Edit: Sorry, hit the wrong button. Didn't mean to close it.
[!NOTE]