Contributions are welcome — issues, fixes, ideas, or full features. To keep things smooth, a few quick guidelines.
- Check the issue tracker of the repo you want to contribute to. Someone may already be working on the same thing.
- Open an issue first for non-trivial changes. A short discussion saves time on both sides — better to align on approach before writing code.
- For typos and small fixes, just open a PR directly.
- Fork the repo and create a topic branch from
main(or the default branch). - Follow existing patterns. Match the codebase's style, naming, and structure rather than introducing new ones.
- Add tests for new behavior. Don't lower coverage. Run the test suite and lint before submitting.
- Keep PRs focused. One concern per PR; smaller PRs land faster.
- Write a clear PR description. What changed, why, and how to verify it.
- Commit messages: Conventional Commits
(
feat:,fix:,docs:,chore:,refactor:,test:,ci:). - Code style: whatever the repo already uses (linter config + formatter in CI). Don't reformat unrelated lines.
- Documentation: update the README and any relevant docs in the same PR as the code change.
By participating you agree to follow the Code of Conduct.
Open a GitHub Discussion (if enabled on the repo) or email contact@techquests.dev.