Link to the Prometheus's contributing guide (#1745)
Signed-off-by: Simon Pasquier <spasquie@redhat.com>
This commit is contained in:
parent
41c5b5cefa
commit
f809c45f4e
|
@ -1,18 +1,3 @@
|
||||||
# Contributing
|
# Contributing
|
||||||
|
|
||||||
Alertmanager uses GitHub to manage reviews of pull requests.
|
Please check the [Prometheus contributing page](https://github.com/prometheus/prometheus/blob/master/CONTRIBUTING.md).
|
||||||
|
|
||||||
* If you have a trivial fix or improvement, go ahead and create a pull request,
|
|
||||||
addressing (with `@...`) the maintainer of this repository (see
|
|
||||||
[MAINTAINERS.md](MAINTAINERS.md)) in the description of the pull request.
|
|
||||||
|
|
||||||
* If you plan to do something more involved, first discuss your ideas
|
|
||||||
on our [mailing list](https://groups.google.com/forum/?fromgroups#!forum/prometheus-developers).
|
|
||||||
This will avoid unnecessary work and surely give you and us a good deal
|
|
||||||
of inspiration.
|
|
||||||
|
|
||||||
* Relevant coding style guidelines are the [Go Code Review
|
|
||||||
Comments](https://code.google.com/p/go-wiki/wiki/CodeReviewComments)
|
|
||||||
and the _Formatting and style_ section of Peter Bourgon's [Go: Best
|
|
||||||
Practices for Production
|
|
||||||
Environments](http://peter.bourgon.org/go-in-production/#formatting-and-style).
|
|
||||||
|
|
Loading…
Reference in New Issue