grafana/contribute/backend
2023-11-03 14:33:12 +01:00
..
communication.md Docs: Update backend contribution guidelines (#63034) 2023-02-07 15:44:56 +01:00
database.md Chore: Move all backend contribution documents to a single directory (#61140) 2023-01-11 11:16:52 +01:00
errors.md Instrumentation: Handle context.Canceled (#75867) 2023-10-10 12:28:39 +02:00
instrumentation.md Tracing: Standardize on otel tracing (#75528) 2023-10-03 14:54:20 +02:00
package-hierarchy.md Chore: Move all backend contribution documents to a single directory (#61140) 2023-01-11 11:16:52 +01:00
README.md Docs: Update references in contribute/ dir (#69564) 2023-06-06 15:56:39 +02:00
recommended-practices.md Docs: Update backend contribution guidelines (#63034) 2023-02-07 15:44:56 +01:00
services.md Chore: Move backgroundsvcs and usagestatssvcs to registry (#72692) 2023-08-02 09:25:55 -04:00
style-guide.md Docs: Improve our mocks section (backend style guide) (#77615) 2023-11-03 14:33:12 +01:00
support-bundles.md SupportBundles: Add support bundle documentation (#61855) 2023-02-07 04:39:47 -05:00
upgrading-dependencies.md Chore: Move all backend contribution documents to a single directory (#61140) 2023-01-11 11:16:52 +01:00

Backend

First read the backend style guide to get a sense for how we work to ensure that the Grafana codebase is consistent and accessible. The rest of the backend contributor documentation is more relevant to reviewers and contributors looking to make larger changes.

For anyone reviewing code for Grafana's backend, a basic understanding of content of the following files is expected:

Reviewers who review large changes should additionally make a habit out of familiarizing themselves with the content of /contribute/backend from time to time.

Dependency management

Refer to: