- RFCs (requests for comment)
- Code reviews
- Go style guide
- Continuous releasability
- Commit message guidelines
Each Sourcegraph engineer works on a team that has long-term ownership of a part of our product and codebase. See the project roadmap for what each team is working on.
Sourcegraph has a lot of repositories!
Where Sourcegraph is built (things you’ll find out-of-the-box):
- Main repositories
- Web development repositories
- Backend repositories
- Tooling repositories
- Documentation repositories
How Sourcegraph gets deployed:
Where Sourcegraph gets extended functionality:
How Sourcegraph operates as a business
This point lives here for now:
- We require passing checks on GitHub PRs before merging (and don’t allow direct pushes to master). Sometimes it’s nice to push without waiting for checks (such as for docs-only changes), but this is outweighed by the downside that people too often accidentally merged changes that broke the build. Certain kinds of low risk changes (e.g., documentation only changes) may only run a subset of the build pipeline so that checks pass quickly in those cases.