chore: Reconfigure GitHub workflows

[kachkaev]

Description

This PR addresses #2080 (review).

The yaml is inspired by gicentre/prettier-plugin-elm → .github/workflows/check-codebase.yml.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• xNew feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as before)
• Chore (CI updates)

Checklist

• Read the Contributing Guide
• Perform a code self-review
• Comment the code, particularly in hard-to-understand areas
• Add documentation
• Add hook's story at Storybook
• Cover changes with tests
• Ensure the test suite passes (yarn test)
• Provide 100% tests coverage
• Make sure code lints (yarn lint). Fix it with yarn lint:fix in case of failure.
• Make sure types are fine (yarn lint:types).

[streamich]

Maybe, let's drop Windows? It takes too long:

[streamich]

Looks great, thank you!

[kachkaev]

Yeah yarn install is not the fastest on Windows. I removed it from the MVP for now, it it might be worth re-adding this OS to later for robustness (at least Node LTS). The install might get faster once we’ve upgraded all project deps. I suspect that we’re dealing with some binary package that is built on the fly — 4 minutes for yarn install is quite a lot 🤔

Happy to bring Windows back now if you’ve changed your mind 🙂

[streamich]

Happy to bring Windows back now if you’ve changed your mind 🙂

Let's remove it for now, we can always add it later if there is need.

[kachkaev]

👍 Done in 2cc1983

[streamich]

👍 Done in 2cc1983

Great, you should be able to merge it.

[kachkaev]

Thanks! Happy for you to merge the PR – I’m not sure if there is a preferred policy:

I usually have this in the repo settings:

[kachkaev]

@streamich which merge type would you recommend?

[streamich]

@streamich which merge type would you recommend?

Either way is fine, but the final merge should contain the right semantic commits so that semantic-release will automatically release the right version.

If somebody uses semantic Angular-style commits, I would merge using "Merge commit", if not, I would squash and add the right commit type in the squash commit message.

[streamich]

@kachkaev Thanks, good improvement!

[streamich]

🎉 This PR is included in version 17.3.2 🎉

The release is available on:

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

Your semantic-release bot 📦🚀