[test] Skip expensive GitHub actions on l10nbot commits

[eps1lon]

Ported behavior of azure pipelines and CircleCI to GitHub actions. Now I just need to cancel ~1300 jobs in the queue 😬

Update:
Cancelling queued runs of l10nbot with https://gist.github.com/eps1lon/9c822429bffb5db5a3f221dd00fea842#file-cancel-gh-actions-js

[mui-pr-bot]

No bundle size changes

Generated by 🚫 dangerJS against 7d613bf

[oliviertassinari]

On a related note, does GitHub Actions offer a more generous free tier than CircleCI?

https://docs.github.com/en/free-pro-team@latest/actions/reference/usage-limits-billing-and-administration#usage-limits

[eps1lon]

On a related note, does GitHub Actions offer a more generous free tier than CircleCI?

Isn't that more generous than CircleCI? CircleCI has 4 or 5 while GH Actions has 20 (macOS is understandably smaller since they're more expensive).

[oliviertassinari]

Isn't that more generous than CircleCI?

I was wondering from a CI duration perspective. I don't know the CPU & Memory resources available in each GitHub actions compared to CircleCI.

[eps1lon]

Isn't that more generous than CircleCI?

I was wondering from a CI duration perspective. I don't know the CPU & Memory resources available in each GitHub actions compared to CircleCI.

They seemed pretty fast to me. Right now they don't even need to.

[eps1lon]

Queue has settled again and with GH actions running on this PR I consider it verified that the implementation works as expected.

Note how we just had to cancel the 1300 expensive tasks to get the queue of 3300 tasks cleared. The number of runs is clearly not the problem.

[eps1lon]

Queue has settled again and with GH actions running on this PR I consider it verified that the implementation works as expected.

Well, it verified that they're still runing. Unfortunately, they're also still runing for l10nbot.