feat(MWPW-162733): enforce JIRA ticket number in PR title scope

[sanrai]

Overview

Enforces consistent PR title format requiring JIRA ticket numbers to be in the scope section of the conventional commit format. For example: feat(MWPW-123): add feature

Changes

• Added commitlint configuration to enforce JIRA ticket in scope
• Updated GitHub Action workflow to validate PR titles
• Ensures format type(MWPW-XXX): description is followed

Testing Instructions

1. Create a new PR with these incorrect formats (should fail):

   • feat: add feature
   • feat(foo): add feature
   • feat: MWPW-123 add feature

2. Create a PR with these correct formats (should pass):

   • feat(MWPW-123): add feature
   • fix(MWPW-456): fix bug

3. Try editing an existing PR title to an invalid format - check that the status check fails

Test Instructions

Prerequisites

1. Clone the repository
2. Install dependencies: npm install
3. Ensure you have GitHub access to create PRs

Test Cases

1. Invalid PR Title Formats (Should Fail)

Create PRs with these titles and verify they fail the check:

• feat: add new feature
• feat(frontend): add feature
• MWPW-123 feat: add feature
• feat: MWPW-123 add feature
• feat(MWPW): add feature
• feat(MWPW-ABC): add feature

2. Valid PR Title Formats (Should Pass)

Create PRs with these titles and verify they pass the check:

• feat(MWPW-123): add feature
• fix(MWPW-456): fix bug
• docs(MWPW-789): update readme
• chore(MWPW-101): update dependencies

3. PR Title Editing

1. Create a PR with valid title: feat(MWPW-123): add feature
2. Edit the PR title to invalid format: feat: add feature
3. Verify check fails after edit
4. Edit back to valid format and verify check passes

4. Local Development Check

1. Make local commits with any format
2. Verify local commits aren't affected by this change
3. Only PR titles should be enforced

5. Edge Cases

Test these scenarios:

• Numbers in description: feat(MWPW-123): fix 404 error
• Special characters: feat(MWPW-123): add @ symbol support
• Long descriptions: feat(MWPW-123): add very long feature description that spans multiple words

Expected Results

• GitHub Actions check should appear on PR page
• Failed checks should show clear error message about required format
• Local development workflow should not be affected
• Check should re-run automatically when PR title is edited

How to Report Issues

If you find any issues:

1. Screenshot the error
2. Note the PR title used
3. Document any error messages
4. Create a bug ticket with prefix MWPW-

Resolves: MWPW-162733

[github-actions]

Core Web Vitals Metrics

Metric	Value
LCP	13015.90 s
FID	0.60 ms
CLS	N/A

Recorded at: 2024-11-20T09:19:57.043Z
PR: #202

[github-actions]

Core Web Vitals Metrics

Metric	Value
LCP	15016.20 s
FID	0.60 ms
CLS	N/A

Recorded at: 2024-11-22T08:35:50.382Z
PR: #202