@@ -545,29 +545,6 @@ contributors free time, so there is no guarantee that your
545
545
feature will be added. The *best * way to get the feature
546
546
you need added is to contribute it your self.
547
547
548
- .. _how-to-submit-patch :
549
-
550
- Reporting a bug or submitting a patch
551
- -------------------------------------
552
-
553
- The development of Matplotlib is organized through `github
554
- <https://github.com/matplotlib/matplotlib> `_. If you would like
555
- to report a bug or submit a patch please use that interface.
556
-
557
- To report a bug `create an issue
558
- <https://github.com/matplotlib/matplotlib/issues/new> `_ on github
559
- (this requires having a github account). Please include a `Short,
560
- Self Contained, Correct (Compilable), Example <http://sscce.org> `_
561
- demonstrating what the bug is. Including a clear, easy to test
562
- example makes it easy for the developers to evaluate the bug. Expect
563
- that the bug reports will be a conversation. If you do not want to
564
- register with github, please email bug reports to the `mailing list
565
-
566
-
567
- The easiest way to submit patches to Matplotlib is through pull
568
- requests on github. Please see the :ref: `developers-guide-index ` for
569
- the details.
570
-
571
548
.. _how-to-contribute-docs :
572
549
573
550
Contribute to Matplotlib documentation
@@ -610,7 +587,7 @@ your documents.
610
587
611
588
Once your documentation contributions are working (and hopefully
612
589
tested by actually *building * the docs) you can submit them as a patch
613
- against git. See :ref: `install-git ` and :ref: `how-to-submit-patch `.
590
+ against git. See :ref: `install-git ` and :ref: `pr-guidelines `.
614
591
Looking for something to do? Search for `TODO <../search.html?q=todo >`_
615
592
or look at the open issues on github.
616
593
0 commit comments