Skip to main content
Latitude is open source under the MIT License, and contributions are welcome — code, docs, bug reports, and feature ideas alike.

Contributing Guide

The full contribution guide — making changes, reporting issues, the CLA.

Code of Conduct

The standards we hold ourselves and our community to.

​
Ways to contribute

For typos, small docs fixes, and clearly-scoped bugs, just open a PR. For new features or anything significant, open an issue first so we can discuss the approach — undiscussed changes may be rejected.
If you like the project but don’t have time to contribute code: star the repo, share Latitude with people who’d find it useful or mention it at meetups or in your project’s README.

​
Reporting issues

Search existing issues first. A good bug report has expected vs. actual behavior, exact repro steps, and your environment. Found a security vulnerability? Don’t open a public issue — check out the Security Policy.

​
Opening a pull request

1

Branch from the trunk

Fork and branch from development (our trunk).
2

Keep it small and focused

Split large changes — schema separate from logic, refactors first.
3

Make the checks pass

Run pnpm check, pnpm typecheck, pnpm knip, and pnpm test before pushing.
4

Follow Conventional Commits

Use Conventional Commits for commit and PR titles (e.g. fix(traces): handle empty spans). We squash-merge.
5

Link the issue and sign the CLA

Reference the issue with Closes #123. The first time you open a PR, a bot asks you to sign our Contributor License Agreement — a one-time step. PRs can’t be merged until it’s signed.
We’re a small team, we read everything but may take a few days, longer for big changes. Stale or out-of-scope PRs may be closed, but you’re welcome to reopen.

​
Community

We all hang out in our Slack community — a good place to ask questions and share what you’re building.