-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Nested composite actions #862
Comments
As mention in issue #646 the implementation of |
We are hoping to support this soon, up to a certain depth level of ~9 or so. I'll follow up with more information once this is live. |
This is supported now on dotcom, for more information please see: #646 (comment) The recursion depth is up to 9, if we need to raise this, please let us know your use case and we can do so. Other features may handle reuse cases with depths that large better then we can do in composite, but I'm always open to discussing what limit is reasonable |
Thanks for landing this! When refactoring a workflow where |
Same issue. Looking forward tosee it work. |
I would like to be able to create a composite action that contains other composite actions. This does not seem to currently work.
For example, there are four steps that go into installing Python and using pipenv to install and cache dependencies. I'd like to create a single composite action that does everything involved so I don't have to reproduce all of the steps in each of my workflows. I imagine such an action would look like this:
However, that does not seem to work. I get an error complaining like this when I try to use it.
My presumption is that this means I can't have composite actions inside my composite. I suspect this is a common use case and I'd love to see a solution of some form.
The text was updated successfully, but these errors were encountered: