Skip to content

Latest commit

 

History

History
26 lines (18 loc) · 789 Bytes

File metadata and controls

26 lines (18 loc) · 789 Bytes

Contributing

Quick Start

  1. Fork the repo (or create a branch if you have access)
  2. Create a feature branch: git switch -c feat/description
  3. Make your changes
  4. Commit using conventional format: git commit -m "feat(scope): description"
  5. Push and open a PR

Conventions

  • Commits: type(scope): description — types: feat, fix, refactor, docs, test, chore, ci
  • Branches: feat/, fix/, chore/, docs/ prefixes
  • PRs: one logical change per PR, link issues with Fixes #N

Issues

Use the issue templates when available. Include:

  • Clear title describing the problem or request
  • Steps to reproduce (for bugs)
  • Expected vs actual behavior

Code Style

Follow the existing code style in the project. When in doubt, match what's already there.