grafana/contribute/backend
b murphy c12b125bb1
Docs: Update to US English per Writers Toolkit, plus clean up some grammar (#76298)
Co-authored-by: Jack Baldry <jack.baldry@grafana.com>
Co-authored-by: tonypowa <45235678+tonypowa@users.noreply.github.com>
2024-01-05 16:40:11 +00:00
..
communication.md Docs: Update backend contribution guidelines (#63034) 2023-02-07 15:44:56 +01:00
database.md
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
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: Update to US English per Writers Toolkit, plus clean up some grammar (#76298) 2024-01-05 16:40:11 +00:00
support-bundles.md
upgrading-dependencies.md
upgrading-go-version.md Chore: Upgrade Go to 1.21.5 (#79329) 2023-12-15 10:36:49 +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: