chore: enforce commit formatting on PR titles

[psschwei]

Misc PR

Type of PR

• Bug Fix
• New Feature
• Documentation
• Other

Description

• Link to Issue: Fixes Conventional commits - consider mergify -> native github #681

Enforces mergify rule on PR titles via existing github action that adds labels.
Once this merges, we can disable the mergify action

Testing

• Tests added to the respective file if code was changed
• New code has 100% coverage if code as added
• Ensure existing tests and github automation passes (a maintainer will kick off the github automation when the rest of the PR is populated)

[github-actions]

The PR description has been updated. Please fill out the template for your PR to be reviewed.

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert|release)(?:\(.+\))?:

[psschwei]

We can also add a similar action to mellea-contribs and deprecate mergify for our whole org

[planetf1]

Have you considered github's native checks for metadata on push? That can match a regex without any custom action - built in.

It can enforce on commit, title etc.

[psschwei]

Have you considered github's native checks for metadata on push? That can match a regex without any custom action - built in.

It can enforce on commit, title etc.

As mentioned in the issue, those are only available on an enterprise plan (which we don't have)

[ajbozarth]

I see no issues adding this