We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Calling an action from another workflow means that the output gets aggregated into a single step:
I'd much rather see dropdowns for each individual step:
Doesn't yet seem to be implemented, but has been requested here: community/community#10985
The text was updated successfully, but these errors were encountered:
Could alternatively group my steps into separate actions, and call them with one master action. Similar to how r-lib/actions worked.
r-lib/actions
Sorry, something went wrong.
This might the related to Jobs: https://dev.to/n3wt0n/composite-actions-vs-reusable-workflows-what-is-the-difference-github-actions-11kd
Causes more problems than it solves, currently. Will circle back to do this eventually.
bschilder
No branches or pull requests
Calling an action from another workflow means that the output gets aggregated into a single step:
I'd much rather see dropdowns for each individual step:
Doesn't yet seem to be implemented, but has been requested here:
community/community#10985
The text was updated successfully, but these errors were encountered: