GitHub Actions - Orange-OpenSource/Orange-Boosted-Bootstrap GitHub Wiki

Run GitHub actions again

In case you're facing a workflow that doesn't cancel and cannot be re-run, the only way I found is to trigger a new build using an empty commit:

git commit --allow-empty -m "ci(tests): trigger Github Actions"

I recommend using this exact commit message to ease their identification.

Required checks early bail

Some checks are set as required to protect branches, but should not be triggered if related files are left unchanged. So instead of adding paths conditions for each workflow —which would prevent them from running albeit being required, so you'd get stuck with actions "waiting for statuses"— there're a few labels to set on your PR to make them bail early:

• skip:ci would bail early every actions,
• skip:browserstack, skip:pa11y and skip:percy will bail early their respective action,
• [skip ci] and [skip netlify] in commit message will prevent Netlify from deploying said commit.

These labels should not be used to ignore failing actions. This is meant to decrease our ecological footprint by saving resources and power, and get low on third-party apps with quota (namely Percy).

GitHub does not allow to skip required checks if paths doesn't match, which is a shame. Alternatives to what I've done here are:

• use paths to completely prevent actions from starting: they'd get stuck as "waiting" but team members could still use their administrator privileges to merge.
• add a doublon action with the same name but the opposite conditions— that will success every time. Mostly a hack.
• use a branch naming convention (e.g. ci/ or chore/ would not trigger CI) by setting branches-ignore: rule everywhere— but I find this way more confusing.

Note: paths restrictions are still in place for push events.