8000 Explain the requirements for converting bpo patch to GitHub by Mariatta · Pull Request #236 · python/devguide · GitHub
[go: up one dir, main page]
Skip to content

Explain the requirements for converting bpo patch to GitHub #236

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
Jun 30, 2017
Merged

Explain the requirements for converting bpo patch to GitHub #236

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
13 changes: 13 additions & 0 deletions pullrequest.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -259,6 +259,19 @@ The commits will be squashed when the pull request is merged.

.. _issue tracker: https://bugs.python.org

Converting an Existing Patch from the b.p.o to GitHub
-----------------------------------------------------

When a patch exists in the `issue tracker`_ that should be converted into a
GitHub pull request, please first ask the original patch author to prepare
their own pull request. If the author does not respond after a week, it is
acceptable for another contributor to prepare the pull request based on the
existing patch. In this case, both parties should sign the :ref:`CLA <cla>`.
When creating a pull request based on another person's patch, provide
attribution to the original patch author by adding "Original patch by
<author name>." to the pull request description and commit message.

See also :ref:`Applying a Patch from Mercurial to Git <git_from_mercurial>`.

Reviewing
---------
Expand Down
0