Support utilizing checks with dynamic configs
X
Xinxing Jiang
At the moment, dynamic configs are very helpful for isolating and running a specific subset of a configuration file. However, when it comes to checks, and reporting if a workflow or job passed, it can sometimes lead to PR's not being able to be merged since specific items were not executed. There should be a way to support checks with using the dynamic config feature.
Jan Vilimek
We have dynamic configs too in our monorepo. We configured the GitHub to do the required checks for the static workflow (the one that executes path-filtering and continuation). Which is a pity as once it's executed (like in 3s) the PR is able to be merged even the mono workflow are still in progress. If those fail, the PR can't be merged, but there is this window, when yes..
A
Alon Reches
A feature allowing this will be super helpful for us and will allow us to avoid "dummy-checks" or the alternative of one workflow for a very big monorepo
V
Victor Tso-Guillen
Agree on this request. We are handcoding each workflow with a job that requires all the other jobs to succeed, and calling this job the same name across workflows. We are then gating PR merges on this success job running and succeeding. This works fine if our dynamic configs fires only one of the workflows, but not sure if it works when multiple workflows fire. Our workplace treats this as an edge case, but may not be in a larger monorepo.