Files
pipdock/.github/PULL_REQUEST_TEMPLATE.md
T
poli0981andClaude Opus 5.5 61e5e26c4e ci: close feature requests in maintenance mode, and say why
triage.yml labels a feature request enhancement and out-of-scope,
answers in English and Vietnamese with CONTRIBUTING linked, and closes
it as not planned — on unmistakable signals only: a title that says it
is one, a feat: pull request, or the enhancement label going on.
Maintainers, bots and policy-exception are never closed. The rules live
in .github/scripts/triage.cjs with node --test cases (run by npm
licences); pull_request_target checks out only the base branch's
scripts; workflow_dispatch is a dry run. notify.yml hears about it.

Templates: a Wording or translation form (i18n), a contact link saying
features are not taken, a maintenance note on the bug form, and the
kinds of change a pull request can be. eslint.config.js lints the
CommonJS helper as Node, outside the type-aware program.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-21 23:22:12 +07:00

2.2 KiB

What kind of change

  • A bug fix
  • A UI/UX defect
  • An accessibility barrier
  • Wording or a translation (English or Vietnamese)
  • A dependency, runtime or toolchain update
  • A security fix
  • Documentation

What this changes

How it was checked

  • A test fails without this change and passes with it
  • npm run lint, npm run typecheck, npm test
  • cargo fmt --check, cargo clippy --workspace --all-targets -- -D warnings, cargo test --workspace --locked

If it touches…

  • A Rust type that crosses to the UI — bindings regenerated (cargo run -p xtask -- bindings)
  • CLI output — goldens re-blessed deliberately, and the diff is the change you meant
  • User-visible text — added to both ui/src/locales/en and ui/src/locales/vi; nothing phrased in Rust
  • A new error code — every place CLAUDE.md lists, both errors.json included
  • Behaviour a user reads about — docs/ updated, and legal/ checked separately
  • Something a user would notice — an entry in changelog/

Accessibility (for any change to the interface)

  • Everything new can be reached and operated with the keyboard alone
  • Focus is visible, and goes somewhere sensible when the screen changes or a dialog closes
  • Controls that show only a symbol have an accessible name; inputs have labels
  • Nothing is said by colour alone, and a destructive button carries data-destructive
  • Checked once with a screen reader, or said here that it was not