chore: Add semantic PR Linter

[DaveSkender]

Adding enforcement of semantic conventional commit standards for PR titles.

to do

• update settings, see action docs
  • enforce first letter capitalized, or sentence case
• update PR template with other standards, like BREAKING CHANGE
• consider also Semantic Release convention tooling
• copy to other repos

Note: to test in this initial PR, temporarily change on: pull_request_target to on: pull_request

initial configuration

feat(ui): Add `Button` component
^    ^    ^
|    |    |__ Subject
|    |_______ Scope
|____________ Type

In our implementation:

• types and scopes requirements were not altered, using default settings and values (scope is not required, not do we recommend using it).
• subject was adjusted to required that it starts with a Capitalized letter, for example feat: Poodle doodle would pass, but feat: poodle doodle would fail. This implicitly also means subject cannot start with symbols or numbers.

[github-actions]

✔️ Tests 718 / 718 - passed in 6.6s
✔️ Coverage 96.47% - passed with 95% threshold
📏 5315 / 5318 lines covered 🌿 2309 / 2585 branches covered
🔍 click here for more details

✏️ updated for commit 5cd0db1

[DaveSkender]

Why is it not triggered?

[DaveSkender]

Okay, it works, just not on this initial PR when using on: pull_request_target.

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

It looks like your proposed title needs to be adjusted.

🚩 The subject "add semantic-pr-linter" found in the pull request title "chore: add semantic-pr-linter" didn't match the configured pattern. Please ensure that the subject starts with an uppercase character.

Pull request title naming convention

Our PR title name taxonomy is type: Subject, where type is typically feat, fix, or chore and subject is a noun that starts with a capitalized letter. The chore type usually has a subject that starts with an action verb like Add or Update. Examples:

feat: Admin portal login
fix: Divide by zero bug in SMA
chore: Update user docs

See the Conventional Commits specification for more information.