Reusable workflows: Increase limit of called workflow depth from 2 to 3 or more
See original GitHub issueDescribe the enhancement
I am trying to generalize my resuable workflows. By doing so I hit the maximum depth limit:
error parsing called workflow "./.github/workflows/build.yml@":
job "arch" calls workflow "./.github/workflows/docker-multistage-build.yml@",
but doing so would exceed the limit on called workflow depth of 2
I would like to be able to allow reusable workflows to call other reusable workflows and then call the initial one in my main workflow
Issue Analytics
- State:
- Created a year ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
How can I reuse a GitHub Actions workflow from the branch ...
I'd like to abstract some of my GitHub Actions with a reusable workflow. In order to do this, I need to call my...
Read more >How to start using reusable workflows with GitHub Actions
Reusable workflows offer a simple and powerful way to avoid copying and pasting workflows across your repositories.
Read more >GitHub Actions: Improvements to reusable workflows
You can now nest up to 4 levels of reusable workflows giving you greater flexibility and better code reuse. Calling a reusable workflow...
Read more >Composite Actions vs Reusable Workflows
This means you can create a Composite Action that has another Composite Action as one of its steps, and so on so forth...
Read more >GitHub Actions limitations and gotchas
I want to share whole jobs across my repos, including matrixes and all. I could wrap some common workflows into one action, but...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
then why did I just now get “but doing so would exceed the limit on called workflow depth of 3”?
Because the total depth is 4, including the top level workflow, so the called workflow depth limit is 3.
That said, this really reeks of an artificial limitation or suboptimal implementation, and is extremely limiting from an encapsulation and composability perspective. I hope there are plans in progress to address whatever the root failure is and remove this limit entirely (or set it to a number that no sane workflow can reach).