This document sets guidelines for how we approach software development at Sentry.
This guide steps you through configuring a local development environment for the Sentry server on macOS and Linux.
We have very precise rules over how our git commit messages can be formatted. This leads to more readable messages that are easy to follow when looking through the project history.
We run several kinds of tests at Sentry as part of our CI process. This section aims to document some of the sentry specific helpers and give guidelines on what kinds of tests you should consider including when building new features.
Code review is mandatory at Sentry. This adds overhead to each change, but ensures that simple, often overlooked problems are more easily avoided.
Sentry uses a variety of continuous integration services to help ensure we don't accidentally break the application.
Sentry is a product used and developed by many people from different cultural backgrounds, and we try to avoid language that has been identified as hurtful or insensitive.
A part of every development project (especially Open Source projects) is documentation that explains how it works. Sentry is not any different.
This guide steps you through instrumenting your code with Sentry's 3rd-party analytics infrastructure.
This is a document that contains a bunch of useful resources for getting started with Rust and adhering to our coding principles.