I recently learned about the “[skip ci]” “feature” that allows a committer to skip CI if they put “[skip ci]” or “[ci skip]” in their commit message. And it follows that commit through merges. I understand the desire for such a “feature”, though I am not sure it is a good idea – just because you can, doesn’t mean you should… I especially don’t like the fact that it follows merges.
But now I am noticing that it does not apply to approval type jobs, which seems weird.
Is there a way we can prevent the skip from following through a merge?
Is the fact that the skip doesn’t apply to approval jobs intentional?
Is there a way we can run a workflow that has been skipped, especially after the merge?