@CONTRIBUTING.md
Before drafting any pull request description, strictly adhere to the rules in CONTRIBUTING.md above.
CONTRIBUTING.md@CONTRIBUTING.md in rule definitions so that PR formatting rules are injected into context whenever PR workflows run.fix: / feat:: User-visible changes ONLY.build: / build(release):: Internal release tooling (dev/release/), developer workflows, and build scripts. Always prefer build(release): over chore: or chore(release):.docs:: Documentation and issue templates (.github/ISSUE_TEMPLATE/).ci:: .bazelci and Buildkite CI configurations.workflow: / workflows:: GitHub Actions workflow configurations (.github/workflows/).tests:: Test-only changes and test-helper fixes (never fix: or fix(tests):).agents: / agents(<scope>):: Agent rules, skills, and prompts (.agents/).refactor:: Internal refactoring and fixes for unreleased changes. Never use fix: or feat: unless modifying released, user-visible behavior.Work towards #<issue>)."do not merge" label to the PR when the PR description contains open questions (e.g., gh pr edit <pr> --repo bazel-contrib/rules_python --add-label "do not merge").TODO items, or “Things we could do / follow-up” notes. Evaluate each item against the diff and project rules, flag unresolved items with ACTION_REQUIRED or USER_DECISION_REQUIRED, and verify the "do not merge" label is applied if open questions remain.