Skip to content

Commit 8f52c28

Browse files
story645QuLogic
andcommitted
turned send to matplotlib into a section and added some more info so it would stand out
Co-authored-by: Elliott Sales de Andrade <[email protected]>
1 parent 2cb8c6a commit 8f52c28

File tree

1 file changed

+10
-2
lines changed

1 file changed

+10
-2
lines changed

doc/devel/contribute.rst

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -227,6 +227,9 @@ Maplotlib repository to your own computer, or alternatively using
227227
in-browser development environment that comes with the appropriated setup to
228228
contribute to Matplotlib.
229229

230+
Workflow overview
231+
^^^^^^^^^^^^^^^^^
232+
230233
A brief overview of the workflow is as follows.
231234

232235
#. `Create an account <https://github.com/join>`_ on GitHub if you do not
@@ -289,8 +292,13 @@ A brief overview of the workflow is as follows.
289292

290293
git push -u origin my-feature
291294

292-
Finally, go to the web page of your fork of the Matplotlib repo, and click
293-
'Pull request' to send your changes to the maintainers for review.
295+
Open a pull request on Matplotlib
296+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
297+
Finally, go to the web page of *your fork* of the Matplotlib repo, and click
298+
**Compare & pull request** to send your changes to the maintainers for review.
299+
The base repository is ``matplotlib/matplotlib`` and the base branch is
300+
generally ``main``. For more guidance, see GitHub's `pull request tutorial
301+
<https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork>`_.
294302

295303
For more detailed instructions on how to set up Matplotlib for development and
296304
best practices for contribution, see :ref:`installing_for_devs`.

0 commit comments

Comments
 (0)