ci: lint and commitlint in its own workflow

[jginsburgn]

Fixes #311

[jginsburgn]

Tell me if I am wrong. @devoto13 wants linting (commit and source) to be done in a job under the test.yml workflow and @XhmikosR prefers it to be done in its own workflow (i.e. lint.yml). I can go with both. Let's just get to an agreement.

[XhmikosR]

IMHO opinion commitlint shouldn't block the other tests, so the only way to achieve this is to have it in a separate workflow (separate workflow doesn't necessarily mean a separate workflow file BTW, although it wasn't possible to restart individual workflows until recently).

[jginsburgn]

IMHO opinion commitlint shouldn't block the other tests, so the only way to achieve this is to have it in a separate workflow (separate workflow doesn't necessarily mean a separate workflow file BTW, although it wasn't possible to restart individual workflows until recently).

I agree that it should not block other tests.

IIUC there is a one-to-one relation between a workflow and a file (reference).

Also, besides doing linting in its own workflow, we can do it in its own job and use if: ${{ always() }} for the other testing jobs to make sure they run regardless of the success status of the linting one (reference).

[XhmikosR]

Nowadays, you can restart single workflows, so we can just have one workflow file. I'll let you decide, I don't have strong feelings about it as long as the other tests are not blocked.

[jginsburgn]

Nowadays, you can restart single workflows, so we can just have one workflow file. I'll let you decide, I don't have strong feelings about it as long as the other tests are not blocked.

I prefer its own file. Are you good with that @devoto13 ?

[devoto13]

Are you good with that @devoto13 ?

Everything LGTM

[karmarunnerbot]

🎉 This PR is included in version 5.0.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀