Mikolaj Wielgus 594bb51a57 chore: Use `committed` instead of `conventional-pre-commit` ... The most important difference in this PR is that we now enforce scope and subject line length. `conventional-pre-commit`, which we have been using until now, does not appear to allow that unlike `committed` which we will be now using. On the other hand, `committed` doesn't allow to require having a scope, unlike `conventional-pre-commit`, but I will probably submit them a PR for this later. I also find it questionable that disabling particular checks is to be done by switching boolean options to false. Doing so by string options would be more future-proof. Also note that this has a check to make sure the commit message starts with a verb. I am fine with this myself, but it may be an overkill.		2025-04-30 11:22:23 +00:00
..
build_and_test.yaml	ci: remove file inclusions and exclusions	2025-03-10 02:45:21 +01:00
check_formatting.yaml	chore: Use `committed` instead of `conventional-pre-commit`	2025-04-30 11:22:23 +00:00
check_licensing.yaml	chore(ci): correct name of `check_licensing` flow	2024-12-30 01:07:27 +01:00