Submitting a PR
Contributions are welcome. Here’s how to get a pull request merged smoothly.
Before you start
Section titled “Before you start”For anything beyond a small bug fix, open an issue first to discuss the change. This avoids wasted effort if the direction doesn’t fit the project.
Workflow
Section titled “Workflow”- Fork the repository on GitHub
- Create a branch:
git checkout -b your-feature-name - Make your changes
- Test locally with
npm run tauri dev - Commit with a clear message describing why, not just what
- Push and open a PR against the
devbranch
PR checklist
Section titled “PR checklist”- Tested on macOS with both Apple Silicon and Intel if possible
- No new dependencies added without discussion
- UI changes include a screenshot or short video in the PR description
- Commit messages are clear and descriptive
Code style
Section titled “Code style”Needle uses ESLint and Prettier. Run npm run lint before submitting. The CI will check this too.
Questions
Section titled “Questions”Open a GitHub Discussion ↗ if you’re unsure about anything before diving in.