Files
bookorbit/.github/pull_request_template.md
T
neon e89f4ce0e4 ci: enforce PR issue references and branch conventions
Validate BO-<issue>-<slug> branch names and lint PR titles and commit headers in CI and release workflows.

Require GitHub closing-keyword issue references and verify referenced issues exist. Align contributing, release, commit, testing, and policy docs with the enforced behavior and tone.
2026-05-17 13:10:32 -06:00

1.7 KiB

Before you submit

New feature? Please open an issue first and get approval from the maintainers before writing any code. PRs that introduce features without a prior discussion will be closed.

Used AI assistance? That's fine - but make sure you've read and understood every line of the diff before submitting. PRs that show no sign of self-review will be closed without detailed feedback.

Keep it focused. One thing per PR. Don't bundle a bug fix with a refactor or unrelated cleanup. If it's not ready, open it as a draft instead.


What does this PR do?

Closes #

How did you test this?

Screenshots

Anything non-obvious in the diff?

Checklist

  • I've read through my own diff
  • This PR was discussed in an issue and has maintainer approval (for new features)
  • Lint and tests pass locally
  • No unintended files included (build artifacts, .env, personal configs)