FDN-4209 Update pr-validator workflow

[jlogeart]

Resolves FDN-4209

This PR adds the pr-validator workflow to ensure PRs have associated JIRA tickets.

[coderabbitai]

Warning

Rate limit exceeded

@jlogeart has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 10 minutes and 26 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 339a5d3 and 46be28a.

📒 Files selected for processing (1)

• .github/workflows/pr-validator.yml (2 hunks)

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull Request Overview

This PR updates the pr-validator workflow to enforce stricter JIRA ticket requirements in PR titles. The workflow now validates that PRs start with a properly formatted JIRA ticket identifier rather than allowing tickets anywhere in the title or description.

Key changes:

• Adds 'synchronize' event trigger to validate PR titles on every push
• Removes PR description validation, requiring JIRA tickets only in titles
• Implements stricter regex pattern requiring tickets at the start of the title with 3+ letter prefixes, 3-6 digit numbers, and excluding all-zero ticket numbers

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[mikeclimbrock]

lgtm