From 1ae3d9b7654708fee57a2f884da62a0be9cb836d Mon Sep 17 00:00:00 2001 From: Evaline Ju <69598118+evaline-ju@users.noreply.github.com> Date: Thu, 25 Jun 2026 08:33:15 -0600 Subject: [PATCH 1/2] :wrench: Allow lowercase prefixes Signed-off-by: Evaline Ju <69598118+evaline-ju@users.noreply.github.com> --- .github/workflows/pr-verifier-required.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/pr-verifier-required.yml b/.github/workflows/pr-verifier-required.yml index 68f818e..5d83d6b 100644 --- a/.github/workflows/pr-verifier-required.yml +++ b/.github/workflows/pr-verifier-required.yml @@ -17,14 +17,14 @@ jobs: pull-requests: read steps: - - name: Enforce PR title prefixes (case-sensitive) + - name: Enforce PR title prefixes uses: deepakputhraya/action-pr-title@3864bebc79c5f829d25dd42d3c6579d040b0ef16 # v1.0.2 with: # Union of conventional and template-derived categories allowed_prefixes: > Build,Chore,CI,Docs,Feat,Fix,Perf,Refactor,Revert,Style,Test, Feature,Bug fix,Proposal,Breaking change,Other,Other/Misc - prefix_case_sensitive: true + prefix_case_sensitive: false min_length: 8 env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} From ef119f25cb456421a79f78878ff4de9f5227f1a6 Mon Sep 17 00:00:00 2001 From: Evaline Ju <69598118+evaline-ju@users.noreply.github.com> Date: Thu, 25 Jun 2026 08:40:31 -0600 Subject: [PATCH 2/2] :wrench: Update PR template Signed-off-by: Evaline Ju <69598118+evaline-ju@users.noreply.github.com> --- .github/pull_request_template.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index 92327cd..941cfc1 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -13,7 +13,7 @@ These rules are validated by a required workflow and enforced via GitHub Repository Rulesets, which can block a PR from merging if the title does not meet the prefix or formatting requirements. -✔ Allowed prefixes (must be EXACT, case-sensitive): +✔ Allowed prefixes (case-insensitive): Build, Chore, CI, Docs, Feat, Fix, Perf, Refactor, Revert, Style, Test, Feature, Bug fix, Proposal, Breaking change, Other/Misc @@ -21,11 +21,10 @@ if the title does not meet the prefix or formatting requirements. ✔ Formatting rules: - Prefix must appear at the **very start** of the title. - - Prefix must match EXACT CASE (this is enforced by our PR Title - workflow, which validates exact-match prefixes via the - `allowed_prefixes` input of the GitHub Action used). [3](https://kitemetric.com/blogs/automate-github-actions-updates-organization-wide-efficiency) + - Prefix matching is case-insensitive (e.g. fix, Fix, and FIX are all valid) + and validated via the `allowed_prefixes` input of the GitHub Action used. [3](https://kitemetric.com/blogs/automate-github-actions-updates-organization-wide-efficiency) - Title must be **at least 8 characters long** (enforced by the workflow). - - Use a colon or a space after the prefix (e.g., `Feat: Add feature`). + - Use a colon or a space after the prefix (e.g., `Feat: Add feature`) - recommended. If your PR title doesn't meet these rules, the required workflow will fail and merging will be blocked until fixed.