GeezerVison

Summary

GitHub's merge queue runs merge_group checks on a branch it creates itself, gh-readonly-queue/<base>/pr-<N>-<sha>, and GITHUB_REF_NAME holds that name. CC201 rejected it. Because the Action's branch input defaults to true, a repository that has a merge queue and makes Commit Check a required check (which GitHub then also requires on merge_group) failed every queue entry.

The name is now accepted next to main, master, develop, HEAD and PR-*. Nobody picks this name, so it passes whatever allow_branch_types or allow_branch_names are set to.

Before vs after

$ git checkout --detach
$ GITHUB_ACTIONS=true GITHUB_REF_NAME=gh-readonly-queue/main/pr-12-0123456789abcdef \
  GITHUB_REF_TYPE=branch commit-check -b --no-banner

Changes

• commit_check/rule_builder.py: adds gh-readonly-queue/.+ to the built-in branch names.
• README.md: the allow_branch_names row lists it.
• Tests: the built-in names pattern; the queue branch passes with default config, custom types, and custom names; the bare gh-readonly-queue and a prefixed name are still rejected.

Testing

• pytest: 1451 pass. The one failure, test_load_config_file_permission_error, happens only because the tests ran as root locally. It is unrelated.
• Coverage stays at 100% lines and branches, and ruff check / ruff format --check are clean.

Once this ships, the site's rules.md, configuration.md and example.md lines that list the always-accepted names can add it.