What do you think about adding a commithook to already check this while commiting and not having to wait for the pipeline, if not commit with --no-verify?

I didn't quite understand you. Can you give an example?

A git hook is something that hooks into your git lifecycle. So for example, a pre-commit-hook for example will run exactly before you commit. It is a simple bash script which aborts the lifecycle if it exits with a non zero return value.

So you could run tests as a pre-commit hook and don't allow to commit if some tests fail for example.
You could skip the git hooks with git commit --no-verify, but you have to want to do it, it will not happen automatically.

In our case we would need a commit-msg hook. There are mostly a bunch of tools for every language available, to make this as easy usable as possible. But in general they are just bash script which are placed in the repository :.git/hooks/.

This is the first one I've found: https://github.com/swellaby/rusty-hook

That way, you could see that your commit message is wrong without having to wait for the github action pipelines to finish.

Thank you! I will think about it.