I just noticed that the repository is already using the typos tool, but only for checking documentation. Should I leave spelling workflow as is, or would it be better to add the config file to the existing validate workflow and run it on all files? Alternatively, I can remove the new separate workflow for spelling and stick with checking only the docs as before?
Sorry for the inconvenience. I didn’t notice this before opening the PR. 🤦

I just noticed that the repository is already using the typos tool, but only for checking documentation. Should I leave spelling workflow as is, or would it be better to add the config file to the existing validate workflow and run it on all files? Alternatively, I can remove the new separate workflow for spelling and stick with checking only the docs as before? Sorry for the inconvenience. I didn’t notice this before opening the PR. 🤦

Nothing to worry about. As a reviewer, I have forgotten we have added it.
Feel free to improve the existing setup.

@atilsensalduz - this repository can (currently) only accept commits with valid signatures... Would you be able to set up git commit signing (see GitHub's guide @ https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) and then update this PR to contain only signed commits?

Otherwise, we'll need to update this repository settings to accept un-signed commits from third-party contributors (it's fine for us to do this but will take a short while).

Never mind, I've just re-committed these leaving you as the author on record.

Really appreciate the merge, @RomainMuller and @kakkoyun I'll set up GPG signing for my future commits