ci: EXPOSED-725 Enforce commit message rules

[joc-a]

Detailed description:

• What:
  Ensure that all commit messages in a pull request, including the pull request's title, adhere to the Conventional Commits specification.
• Why:
  The commit message rule is being forgotten sometimes, so it's better to automate this check. Ensuring we adhere to the Conventional Commits specification makes it easier to categorize the commits when preparing the ChangeLog for the release.
• How:

1. Added commit-message-validation.yml that runs a bash script to check the commit messages using a regular expression. The validate-commits job will run when the pull request is first opened and on every push.
2. Added pull-request-title-validation.yml that runs a bash script to check the pull request's title using a regular expression. The validate-PR-title job will run on every edit of the pull request. It's not possible to isolate this to title edits only at the moment, so edits to other parts like the body and labels will also trigger this workflow.

What you'll see when all commit messages are valid:

What you'll see when some commit messages are invalid:

What you'll see when the PR title is valid:

What you'll see when the PR title is invalid:
Example 1

Example 2

---

Type of Change

Please mark the relevant options with an "X":

• Bug fix
• New feature
• Documentation update
• Other - CI

Updates/remove existing public API methods:

• Is breaking change

Affected databases:

• MariaDB
• Mysql5
• Mysql8
• Oracle
• Postgres
• SqlServer
• H2
• SQLite

Checklist

• Unit tests are in place
• The build is green (including the Detekt check)
• All public methods affected by my PR has up to date API docs
• Documentation for my change is up to date

---

Related Issues

[obabichevjb]

In general I like that idea, I also sometimes forget about it)

Just to confirm, if a PR has several commits, that rule for commit message would be applied only to the last one, right?

And there is a moment when we merge the PR. We could squash commits and update the message, that rules wouldn't applied to the new message?

[joc-a]

Just to confirm, if a PR has several commits, that rule for commit message would be applied only to the last one, right?

No, it would apply to all the commits.

And there is a moment when we merge the PR. We could squash commits and update the message, that rules wouldn't applied to the new message?

Yes, when using "Squash and merge", it is possible to modify the final commit message to something that does not conform to the rules, but this is not something within our control and we cannot enforce it with GitHub Actions as far as I know. There could be something in the repository settings that allows us to do this, but I do not have access to them. Do you? @obabichevjb