Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
39 lines (27 loc) · 981 Bytes

CONTRIBUTING.md

File metadata and controls

39 lines (27 loc) · 981 Bytes
Raw

Contributing

Before opening a change

  1. Select the repository that owns the affected behavior.
  2. Search existing issues and pull requests.
  3. Reproduce defects and record the environment, current behavior, and expected behavior.
  4. Keep the change focused and preserve existing supported behavior.

Development

npm ci
npm run dev

Required checks

npm run validate
npm run audit:prod

A pull request must not introduce build errors, type errors, inaccessible controls, broken internal links, unapproved brand colors, new fonts, non-Lucide icons, or unnecessary client JavaScript.

Commit scope

Use clear, imperative commit messages. Separate unrelated refactors from functional changes.

Pull request evidence

Include:

  • Purpose and affected routes
  • Screenshots at relevant responsive widths for visual changes
  • Keyboard and focus verification
  • Build and validation results
  • Backward-compatibility impact
  • Security implications