3.17 KB
Newer Older
Stuart Nelson committed
1 2
# Contributing

3 4
Prometheus uses GitHub to manage reviews of pull requests.

5 6
* If you are a new contributor see: [Steps to Contribute](#steps-to-contribute)

7 8 9
* If you have a trivial fix or improvement, go ahead and create a pull request,
  addressing (with `@...`) a suitable maintainer of this repository (see
  []( in the description of the pull request.
10 11 12 13

* If you plan to do something more involved, first discuss your ideas
  on our [mailing list](!forum/prometheus-developers).
  This will avoid unnecessary work and surely give you and us a good deal
  of inspiration. Also please see our [non-goals issue]( on areas that the Prometheus community doesn't plan to work on.
15 16 17 18 19 20

* Relevant coding style guidelines are the [Go Code Review
  and the _Formatting and style_ section of Peter Bourgon's [Go: Best
  Practices for Production

Bryan Boreham committed
22 23
* Be sure to sign off on the [DCO](

24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53

## Steps to Contribute

Should you wish to work on an issue, please claim it first by commenting on the GitHub issue that you want to work on it. This is to prevent duplicated efforts from contributors on the same issue.

Please check the [`low-hanging-fruit`]( label to find issues that are good for getting started. If you have questions about one of the issues, with or without the tag, please comment on them and one of the maintainers will clarify it. For a quicker response, contact us over [IRC](

For complete instructions on how to compile see: [Building From Source](

For quickly compiling and testing your changes do:
# For building.
go build ./cmd/prometheus/

# For testing.
make test         # Make sure all the tests pass before you commit and push :)

All our issues are regularly tagged so that you can also filter down the issues involving the components you want to work on. For our labelling policy refer [the wiki page](

## Pull Request Checklist

* Branch from the master branch and, if needed, rebase to the current master branch before submitting your pull request. If it doesn't merge cleanly with master you may be asked to rebase your changes.

* Commits should be as small as possible, while ensuring that each commit is correct independently (i.e., each commit should compile and pass tests).

* If your patch is not getting reviewed or you need a specific person to review it, you can @-reply a reviewer asking for a review in the pull request or a comment, or you can ask for a review on IRC channel [#prometheus]( on (for the easiest start, [join via Riot](

* Add tests relevant to the fixed bug or new feature.