Suppose I have this dependency chain of job:
A → B → C
When B needs A and C needs B. IMPORTANT: C does not need A.
The problematic case is that when A is skipped, C is also skipped regardless of whether B is skipped or not. I don’t think this is desirable because C does not declare that it needs A.
F.ex imagine “A” as a job that populates a cache, B is a job that we want to executed after A, and C is a job that needs the output of B.
The control flow of Github Actions leave a lot to be desired. I think this problem can be solved if we don’t conflate “B depends on A” and “B must be executed after A”.