Use squash merges for feature pull requests

[jaykbpark]

What changed

• Remove the requirement that every pull request already contain exactly one
  commit.
• Validate the pull request title instead, since it becomes the squash commit
  subject.
• Upgrade actions/github-script from v7 to v9 to remove the Node 20
  deprecation warning.
• Document the intended branch strategy:
  • feature/fix branches → dev: squash and merge
  • dev → main: regular merge

Why

The one-commit check was written for feature pull requests but also runs on
release pull requests. PR #448 promotes dev to main, so it correctly
contains the accumulated feature commits and has failed this check since it
opened.

Squashing at merge keeps one commit per feature in dev without forcing
contributors to rewrite their working history. Preserving a regular merge from
dev to main keeps the long-lived branches related.

Repository settings follow-up

This repository currently allows only rebase merges. An admin must enable
Squash merging for feature PRs and Merge commits for dev → main. A
branch ruleset should restrict PRs targeting dev to squash merges if strict
enforcement is desired.

Validation

• Prettier 3.5.3 check passed for the changed files.
• Workflow YAML syntax check passed.
• git diff --check passed.
• Full npm ci is currently blocked by the pre-existing mismatch between
  package.json and package-lock.json; this PR does not change dependencies.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
biztech-v2	Ready	Preview	Sep 7, 2026 11:15pm UTC