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

Lack of clarity re: reusable workflow outputs #32543

Closed
1 task done
APCBoston opened this issue Apr 16, 2024 · 2 comments · Fixed by #32544
Closed
1 task done

Lack of clarity re: reusable workflow outputs #32543

APCBoston opened this issue Apr 16, 2024 · 2 comments · Fixed by #32544
Labels
actions This issue or pull request should be reviewed by the docs actions team content This issue or pull request belongs to the Docs Content team

Comments

@APCBoston
Copy link
Contributor

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/actions/using-workflows/reusing-workflows#using-outputs-from-a-reusable-workflow

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

The existing text is not clear that the workflow level outputs: may be mapped to job-level, but not step-level outputs. The example workflow maps step-level outputs to job-level outputs, then to workflow-level outputs, but the text does not explain that this is needed and that attempting to map workflow-level outputs directly to step-level outputs won't work. Attempts to use step-level outputs do not generate an error but pass an empty output to the caller, compounding the confusion.

Additional information

A proposed clarification will follow momentarily in the form of a PR.

@APCBoston APCBoston added the content This issue or pull request belongs to the Docs Content team label Apr 16, 2024
Copy link

welcome bot commented Apr 16, 2024

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 Apr 16, 2024
@nguyenalex836 nguyenalex836 added actions This issue or pull request should be reviewed by the docs actions team and removed triage Do not begin working on this issue until triaged by the team labels Apr 16, 2024
@nguyenalex836
Copy link
Contributor

@APCBoston Thank you for opening an issue and linking it to your PR! ✨

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
actions This issue or pull request should be reviewed by the docs actions team 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.

2 participants