... ergers handle them, see プルリクエストの取り扱い . Below, we are going to show how to create a GitHub pull request containing the changes for Trac ticket #xxxxx. By creating a fully-ready pull request, you will make the reviewer' ... c branches are the main and stable/A.B.x branches in the django/django repository. When you think your work is ready to be pulled into Django, you should create a pull request at GitHub. A good pull request means: commits with one logical change in e ... umentation changes. The test suite must pass and the documentation must build without warnings. Once you have created your pull request, you should add a comment in the related Trac ticket explaining what you've done. In particular, you should note t ... ... ergers handle them, see プルリクエストの取り扱い . Below, we are going to show how to create a GitHub pull request containing the changes for Trac ticket #xxxxx. By creating a fully-ready pull request, you will make the reviewer' ... c branches are the main and stable/A.B.x branches in the django/django repository. When you think your work is ready to be pulled into Django, you should create a pull request at GitHub. A good pull request means: commits with one logical change in e ... umentation changes. The test suite must pass and the documentation must build without warnings. Once you have created your pull request, you should add a comment in the related Trac ticket explaining what you've done. In particular, you should note t ... ... ly trivial issue, for example changing a word in the documentation, the preferred way to provide the patch is using GitHub pull requests without a Trac ticket. See Working with Git and GitHub for more details on how to use pull requests. "Claiming" t ... ing feature, the change should also contain documentation. When you think your work is ready to be reviewed, send a GitHub pull request . If you can't send a pull request for some reason, you can also use patches in Trac. When using this style, follo ... intainer time. Automated AI Reviews ¶ Do not request automated AI reviews (for example GitHub Copilot or similar tools) on pull requests submitted to the Django repository. These reviews do not replace human review and often generate noise that distr ... ... and the features Django has decided to add. As in any garden, sometimes there are weeds to be pulled and sometimes there are flowers and vegetables that need picking. We need your help to sort out one from the other, and ... whether a ticket describes a real issue and keeping the tracker organized. Bug fixers: anyone can contribute by opening a pull request and working on a solution for a ticket. Reviewers: anyone can review pull requests and suggest improvements. Merge ... ly want you to help! For example, here's the typical lifecycle of a ticket: Alice creates a ticket and opens an incomplete pull request (missing tests, incorrect implementation). Bob reviews the pull request, marks the ticket as "Accepted", sets the ... ... ly trivial issue, for example changing a word in the documentation, the preferred way to provide the patch is using GitHub pull requests without a Trac ticket. See Working with Git and GitHub for more details on how to use pull requests. "Claiming" t ... ing feature, the change should also contain documentation. When you think your work is ready to be reviewed, send a GitHub pull request . If you can't send a pull request for some reason, you can also use patches in Trac. When using this style, follo ... intainer time. Automated AI Reviews ¶ Do not request automated AI reviews (for example GitHub Copilot or similar tools) on pull requests submitted to the Django repository. These reviews do not replace human review and often generate noise that distr ... ... and the features Django has decided to add. As in any garden, sometimes there are weeds to be pulled and sometimes there are flowers and vegetables that need picking. We need your help to sort out one from the other, and ... whether a ticket describes a real issue and keeping the tracker organized. Bug fixers: anyone can contribute by opening a pull request and working on a solution for a ticket. Reviewers: anyone can review pull requests and suggest improvements. Merge ... ly want you to help! For example, here's the typical lifecycle of a ticket: Alice creates a ticket and opens an incomplete pull request (missing tests, incorrect implementation). Bob reviews the pull request, marks the ticket as "Accepted", sets the ... ... m ...\> git checkout -b ticket_TicketNumber upstream/main When your work is ready, push the branch to your fork and open a pull request. See Submitting contributions for the full process. Continuing someone else's work ¶ If you're continuing the work ... from someone else's pull request on GitHub, things can be tricky. You need to pull their branch, but then push it to your GitHub repository fork. R ... un the following, replacing PRNumber and TicketNumber with the actual pull request and Trac ticket numbers: / $ git fetch upstream pull/PRNumber/head:ticket_TicketNumber $ git checkout ticket_T ... ... m ...\> git checkout -b ticket_TicketNumber upstream/main When your work is ready, push the branch to your fork and open a pull request. See Submitting contributions for the full process. Continuing someone else's work ¶ If you're continuing the work ... from someone else's pull request on GitHub, things can be tricky. You need to pull their branch, but then push it to your GitHub repository fork. R ... un the following, replacing PRNumber and TicketNumber with the actual pull request and Trac ticket numbers: / $ git fetch upstream pull/PRNumber/head:ticket_TicketNumber $ git checkout ticket_T ... ... ルリクエストをチェックすることが多くなったら、この git エイリアスが役立つでしょう: [alias] pr = !sh -c \"git fetch upstream pull/${1}/head:pr/${1} && git checkout pr/${1}\" これを ~/.gitconfig に追加し、 upstream を django/django に設定してください。そ ... mmit --amend を使って、コミットの品質が期待通りのものであることを確認しましょう。準備ができたら次のようにします: / $ # Pull in the latest changes from main. $ git checkout main $ git pull upstream main $ # Rebase the pull request on main. $ git c ... ou expect will be pushed to upstream. $ git push --dry-run upstream main $ # Push! $ git push upstream main $ # Delete the pull request branch. $ git branch -d pr/xxxx ...\> REM Pull in the latest changes from main. ...\> git checkout main ...\> git ... ... ルリクエストをチェックすることが多くなったら、この git エイリアスが役立つでしょう: [alias] pr = !sh -c \"git fetch upstream pull/${1}/head:pr/${1} && git checkout pr/${1}\" これを ~/.gitconfig に追加し、 upstream を django/django に設定してください。そ ... mmit --amend を使って、コミットの品質が期待通りのものであることを確認しましょう。準備ができたら次のようにします: / $ # Pull in the latest changes from main. $ git checkout main $ git pull upstream main $ # Rebase the pull request on main. $ git c ... ou expect will be pushed to upstream. $ git push --dry-run upstream main $ # Push! $ git push upstream main $ # Delete the pull request branch. $ git branch -d pr/xxxx ...\> REM Pull in the latest changes from main. ...\> git checkout main ...\> git ... 2026年10月08日