You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/devel/triage.rst
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,7 @@ important tasks:
86
86
* **invite contributors to engage with the community** if the issue requires
87
87
more information or discussion. These discussions can take place in the
88
88
`weekly community meetings <https://scientific-python.org/calendars>`__, or
89
-
on `discourse <https://discourse.matplotlib.org>`_.
89
+
on `discourse <https://discourse.matplotlib.org>`__.
90
90
91
91
.. topic:: Closing issues: a tough call
92
92
@@ -112,8 +112,9 @@ The following workflow is a good way to approach issue triaging:
112
112
#. Is this a usage question?
113
113
114
114
If so, close it with a polite message, point the reporter to use
115
-
`discourse <https://discourse.matplotlib.org>`_ or Stack Overflow instead and
116
-
use the `community support <https://github.com/matplotlib/matplotlib/issues?q=sort%3Aupdated-desc+state%3Aopen+label%3A%22Community+support%22>`_
115
+
`discourse <https://discourse.matplotlib.org>`__ or Stack Overflow instead
116
+
and use the
117
+
`community support <https://github.com/matplotlib/matplotlib/issues?q=sort%3Aupdated-desc+state%3Aopen+label%3A%22Community+support%22>`__
117
118
label, if you have the necessary permissions.
118
119
119
120
#. Is the necessary information provided?
@@ -168,14 +169,14 @@ The following workflow is a good way to approach issue triaging:
168
169
slightly different example, add it to the original issue as a comment
169
170
or an edit to the original post.
170
171
171
-
Label the closed issue with `status: duplicate <https://github.com/matplotlib/matplotlib/issues?q=sort%3Aupdated-desc+state%3Aopen+label%3A%22status%3A+duplicate%22>`_.
172
+
Label the closed issue with `status: duplicate <https://github.com/matplotlib/matplotlib/issues?q=sort%3Aupdated-desc+state%3Aopen+label%3A%22status%3A+duplicate%22>`__.
172
173
173
174
#. Make sure that the title accurately reflects the issue. If you have the
174
175
necessary permissions edit it yourself if it's not clear.
175
176
176
-
#. Add the relevant labels, such as `Documentation <https://github.com/matplotlib/matplotlib/labels?q=documentation>`_
177
-
when the issue is about documentation, `status: confirmed bug <https://github.com/matplotlib/matplotlib/issues?q=sort%3Aupdated-desc+state%3Aopen+label%3A%22status%3A+confirmed+bug%22>`_
178
-
if it is clearly a bug, `New feature <https://github.com/matplotlib/matplotlib/issues?q=sort%3Aupdated-desc+state%3Aopen+label%3A%22New+feature%22>`_
177
+
#. Add the relevant labels, such as `Documentation <https://github.com/matplotlib/matplotlib/labels?q=documentation>`__
178
+
when the issue is about documentation, `status: confirmed bug <https://github.com/matplotlib/matplotlib/issues?q=sort%3Aupdated-desc+state%3Aopen+label%3A%22status%3A+confirmed+bug%22>`__
179
+
if it is clearly a bug, `New feature <https://github.com/matplotlib/matplotlib/issues?q=sort%3Aupdated-desc+state%3Aopen+label%3A%22New+feature%22>`__
179
180
if it is a new feature request, etc.
180
181
181
182
An additional useful step can be to tag the corresponding module e.g.
0 commit comments