Skip to content

DOC: don't advocate deleting main branch #25948

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 22, 2023
Merged

DOC: don't advocate deleting main branch #25948

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 1 addition & 9 deletions doc/devel/development_workflow.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ To keep your work well organized, with readable history, and in turn make it
easier for project maintainers (that might be you) to see what you've done, and
why you did it, we recommend the following:

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

.. note::

It may sound strange, but deleting your own ``main`` branch can help reduce
confusion about which branch you are on. See `deleting main on GitHub`_ for
details.

.. _deleting main on GitHub: https://matthew-brett.github.io/pydagogue/gh_delete_master.html

.. _update-mirror-main:

Update the ``main`` branch
Expand Down