Feature request: Signal "concurrency" unlock after a specific job

[umanghome]

Select Topic Area

Product Feedback

Body

Hi! We have a workflow that runs with concurrency and does not cancel in-progress jobs. The workflow is huge, and at some point mid-way into the workflow, we want to say, "The core jobs are now complete, we can start executing the queued run while we finish the non-core jobs." Is this possible? Example

Terms:
WR1: Workflow run #1
WR2: Workflow run #2


- WR1 starts
- WR1.job-1 starts
- WR1.job-1 completes
- WR1.job-2 starts
- ...
- WR1.job-6 completes
<WR1 signal that the pending runs (WR2 in this example) can begin>
- WR2 starts
- WR2.job-1 starts
- WR1.job-6 starts
<WR1.job-6...job-9 run in parallel with WR1.job-1...job-9>

eg. Start running E2E tests of the next deployment while the current deployment's nodes are being brought up.

[umanghome]

Maybe the workflow can be broken down into smaller workflows and this can be utilized? https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#running-a-workflow-based-on-the-conclusion-of-another-workflow