Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork855
Reorganize git commands#263
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.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
| Reverts python/cpython#111. | ||
| Reason: This commit broke the buildbot. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
This has been moved after the section about backporting.
| The above steps can be executed against any branch you wish to, just replace master | ||
| with an appropriate branch name. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
All the stuff in this chunk either got added to the bootcamp or it was already there
| @@ -454,34 +336,19 @@ Developers can apply labels to GitHub pull requests). | |||
| .. _cherry_picker.py: https://github.com/python/core-workflow/tree/master/cherry_picker | |||
| .. _forking: | |||
| Forking repository | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
This is already in the bootcamp (and somewhere else too).
| Maintaining a repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
After asking around during the sprint, the consensus was to remove this section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Looks great@ezio-melotti. There's a few small items and then it's ready to merge. Thanks 👍
| origin git@github.com:<your-username>/devguide.git (fetch) | ||
| origin git@github.com:<your-username>/devguide.git (push) | ||
| upstream git@github.com:python/devguide.git (fetch) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Since this doc will often be used by contributors that do not have push privileges for CPython, the upstream remote should point tohttps://github.com/python/cpython in the doc here.
Perhaps a note for committers that they should use what you have here for upstream.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
AFAICT, with this URL, they still should be able to fetch. If they try to push they will get an error because they don't have privileges, but that's OK since they are not supposed to push on upstream anyway. Unless I'm missing something, this URL should be fine for both contributors and core devs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Thanks@willingc and@ezio-melotti. I'm thinking it's fine to leave theupstream using SSH url.
For contributors, they would have to configure SSH key anyway.
| ``git push``, or ``git fetch``. | ||
| ``git push``, or ``git fetch``. On Windows, you should also | ||
| :ref:`enable autocrlf <autocrlf>`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
NIce! 👍
| git clone https://github.com/python/cpython | ||
| In order to get a copy of the source code you should first :ref:`fork the | ||
| Python repository on GitHub <fork-cpython>` and then :ref:`create a local | ||
| clone of your private fork and configure the remotes <clone-your-fork>`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
private I know what you are trying to say here but the fork is public. I think it is better to use...clone of your fork and configure...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
"Personal" is probably the word I was looking for, but "your fork" is clear enough without additional qualifiers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I like personal 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I fixed this in#265
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Thanks@ezio-melotti.
Thanks for the reviews! |
Way to go@ezio-melotti on reorganizing 🍰 |
* Move the minimal configuration instructions.* Move the remote configuration instructions.* Move the pushing changes and synching remotes sections.* First cleanup pass.* Remove the "Maintaining a repository" section.* Move the "Reverting a Merged Pull Request" section under "Working with Git".* Fix incorrect markup.
Uh oh!
There was an error while loading.Please reload this page.
This is part of#120. The goal of this PR is to reorganize the git commands, that are currently scattered around a few pages.
The steps are:
The end result will be:
See also#262.