[TECHNICAL] Workflow to validate commit names

[jesmrec]

Workflow to validate Conventional Commits through all the commits inside a PR.

Validation rules:

• Commit name starts for one of this prefixes: docs|fix|feat|chore|refactor|test|style|build|ci
• Then, a colon :
• Then, a blank space
• Then , the description starting for a lowercase character
• Description must have at least 10 chars, to avoid non-descriptive cases

If the commit name starts by Merge or [tx] will be ignored, as special cases

Every commit in the PR must match the rule, otherwise the check will not pass till it fits.

NOTE: scoped to the latest 100 commits. There is no way to know in advance (before the checkout) how many commits conform the current PR. That means, if a PR contains more that 100 commits (very extreme), only the latest 100 will be checked out.

Related Issues

App:

• Add changelog files for the fixed issues in folder changelog/unreleased. More info here
• Add feature to Release Notes in ReleaseNotesViewModel.kt creating a new ReleaseNote() with String resources (if required)

---

QA

[joragua]

Nice improvement @jesmrec! 💯 One comment about calens entry

[joragua]

LGTM! 🙌🏻

[jesmrec]

Merging...