From 84efad936acacc4c730a815a25841e6ea6118239 Mon Sep 17 00:00:00 2001 From: Awesome-Ace22 Date: Tue, 20 Oct 2026 18:28:33 -0400 Subject: [PATCH] chore: allow 'tests' prefix for branch names in PR checks --- .github/workflows/pr-checks.yml | 4 ++-- CONTRIBUTING.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/pr-checks.yml b/.github/workflows/pr-checks.yml index c5cb0fd..c157e96 100644 --- a/.github/workflows/pr-checks.yml +++ b/.github/workflows/pr-checks.yml @@ -26,7 +26,7 @@ jobs: BASE_REF: ${{ github.base_ref }} run: | words='[a-z0-9]+(-[a-z0-9]+)*' - work="^(feature|bugfix|chore)/${words}$" + work="^(feature|bugfix|chore|tests)/${words}$" hotfix="^hotfix/${words}$" release='^release/v[0-9]{4}\.[0-9]{2}\.[0-9]{2}(\.[0-9]+)?$' github_made='^(revert-[0-9]+-|dependabot/)' @@ -34,7 +34,7 @@ jobs: if [[ ! ( "$HEAD_REF" =~ $work || "$HEAD_REF" =~ $hotfix || "$HEAD_REF" =~ $release \ || "$HEAD_REF" == "main" || "$HEAD_REF" =~ $github_made ) ]]; then - fail "Branch '$HEAD_REF' must be named feature/..., bugfix/..., chore/... (lower case, words joined by single hyphens), e.g. bugfix/fas-port-reconnect. Rename it on GitHub (Branches page, pencil icon) - that keeps this PR." + fail "Branch '$HEAD_REF' must be named feature/..., bugfix/..., chore/..., tests/... (lower case, words joined by single hyphens), e.g. bugfix/fas-port-reconnect. Rename it on GitHub (Branches page, pencil icon) - that keeps this PR." fi case "$BASE_REF" in diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index bac3e4b..ad509df 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -5,7 +5,7 @@ Read that first.** In short: - `dev` collects finished work for hardware testing; `main` is what prod runs. -- Branch from `dev` as `feature/...`, `bugfix/...` or `chore/...`, e.g. `bugfix/fas-port-reconnect`. +- Branch from `dev` as `feature/...`, `bugfix/...`, `chore/...` or `tests/...`, e.g. `bugfix/fas-port-reconnect`. - Open a PR **into `dev`**, titled `type(scope): what changed`, and fill in the template. - CI green + 1 approval (a lead's if it can move hardware), then **Squash and merge**. - Leads bring tested releases into `main`; you never merge into `main` yourself.