Preview: ggbecker#14 (comment)

How about using https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows#workflow_run with single if: ${{ steps.ctf.outputs.CTF_OUTPUT_SIZE != '0' }} for the real diff job?

We could be able to use single https://github.com/ComplianceAsCode/content/blob/master/.github/workflows/ctf.yaml workflow as a dependency for all other jobs that require its output.

How about using https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows#workflow_run with single if: ${{ steps.ctf.outputs.CTF_OUTPUT_SIZE != '0' }} for the real diff job?

We could be able to use single https://github.com/ComplianceAsCode/content/blob/master/.github/workflows/ctf.yaml workflow as a dependency for all other jobs that require its output.

we can definitely improve how jobs relate to each other and put them as dependency of each other. I will take a look at this.

How about using https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows#workflow_run with single if: ${{ steps.ctf.outputs.CTF_OUTPUT_SIZE != '0' }} for the real diff job?
We could be able to use single https://github.com/ComplianceAsCode/content/blob/master/.github/workflows/ctf.yaml workflow as a dependency for all other jobs that require its output.

we can definitely improve how jobs relate to each other and put them as dependency of each other. I will take a look at this.

I'm starting to think that this is not a good idea. There are some limitations, for example the job that runs on a workflow_run doesn't know the PR context and after some tries I was not even able to make it work properly (ggbecker#18)

Maybe we can use the same workflow file to accommodate all of these jobs that depend on CTF and use the simple needs keyword.

I have to investigate more. But I think we shouldn't block this one to get merged as we can refactor and improve the jobs later.

Yeah, you're probably right. I just don't like CTF sprawling and wedging all over the place unchecked.