A modern programming language that makes developers happier.

kotlinlang

Oh, so endless loops are hard to create in GH Actions: <https://github.community/t/github-actions-workflow-not-triggering-with-tag-push/17053/6>

Well, not quite :slightly_smiling_face: Now I'm searching for a workaround for that :upside_down_face:

The current situation is that after the generator creates and pushes a new commit, it's better to run our checks for it. But it doesn't happen automatically because that commit was pushed by a workflow, and this doesn't invoke the "push" event, so our checking workflow isn't run :sweat_smile:

Ah, I see - so in fact you don't want to create the endless loop, but run the verification workflow (automatic) once after the generation workflow (manual), right? Maybe the observation that these are two workflows will be any helpful

Even if it's hard or not doable within your designated time, we can go with an assumption for now: what the generating workflow generated is valid. In scope of PR this is bearable because after merging to the main branch, it should be validated right?

Just found official docs on it: <https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows#triggering-new-workflows-using-a-personal-access-token>

Let me just allow to run checks manually too, not only by pushing. It will allow to automatically check generated commits before merging at least somehow