Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit ef56ed5

Browse files
authored
Merge pull request #25948 from rcomer/dont-delete-main
DOC: don't advocate deleting main branch
2 parents f45b423 + e5f9798 commit ef56ed5

File tree

1 file changed

+1
-9
lines changed

1 file changed

+1
-9
lines changed

doc/devel/development_workflow.rst

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ To keep your work well organized, with readable history, and in turn make it
1313
easier for project maintainers (that might be you) to see what you've done, and
1414
why you did it, we recommend the following:
1515

16-
* Don't make changes in your local ``main`` branch! Consider deleting it.
16+
* Don't make changes in your local ``main`` branch!
1717
* Before starting a new set of changes, fetch all changes from
1818
``upstream/main``, and start a new *feature branch* from that.
1919
* Make a new branch for each feature or bug fix — "one task, one branch".
@@ -25,14 +25,6 @@ why you did it, we recommend the following:
2525
Matplotlib developers can give feedback and eventually include your suggested
2626
code into the ``main`` branch.
2727

28-
.. note::
29-
30-
It may sound strange, but deleting your own ``main`` branch can help reduce
31-
confusion about which branch you are on. See `deleting main on GitHub`_ for
32-
details.
33-
34-
.. _deleting main on GitHub: https://matthew-brett.github.io/pydagogue/gh_delete_master.html
35-
3628
.. _update-mirror-main:
3729

3830
Update the ``main`` branch

0 commit comments

Comments
 (0)