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

Skip to content

Commit c26e08e

Browse files
committed
DOC : removed out-dated git advices
It is a bad idea to all push directly to the same repo/branch, that way lies madness/cvs closes matplotlib#3280
1 parent 7d4ac9d commit c26e08e

File tree

1 file changed

+0
-29
lines changed

1 file changed

+0
-29
lines changed

doc/devel/gitwash/development_workflow.rst

Lines changed: 0 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -261,35 +261,6 @@ Deleting a branch on github_
261261
(Note the colon ``:`` before ``test-branch``. See also:
262262
http://github.com/guides/remove-a-remote-branch
263263

264-
Several people sharing a single repository
265-
==========================================
266-
267-
If you want to work on some stuff with other people, where you are all
268-
committing into the same repository, or even the same branch, then just
269-
share it via github_.
270-
271-
First fork matplotlib into your account, as from :ref:`forking`.
272-
273-
Then, go to your forked repository github page, say
274-
``http://github.com/your-user-name/matplotlib``
275-
276-
Click on the 'Admin' button, and add anyone else to the repo as a
277-
collaborator:
278-
279-
.. image:: pull_button.png
280-
281-
Now all those people can do::
282-
283-
git clone [email protected]:your-user-name/matplotlib.git
284-
285-
Remember that links starting with ``git@`` use the ssh protocol and are
286-
read-write; links starting with ``git://`` are read-only.
287-
288-
Your collaborators can then commit directly into that repo with the
289-
usual::
290-
291-
git commit -am 'ENH - much better code'
292-
git push origin master # pushes directly into your repo
293264

294265
Exploring your repository
295266
=========================

0 commit comments

Comments
 (0)