... er upstream/main ...\> git fetch upstream ...\> 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 els ... tinuing 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. Run the following, replacing PRNumber and TicketNumber with the actual pull request and ... ticket numbers: / $ git fetch upstream pull/PRNumber/head:ticket_TicketNumber $ git checkout ticket_TicketNumber $ git push origin ticket_TicketNumber ...\> git fetch upstream pull/PRNumber/head:ticket_TicketNumber ...\> git checkout ticket_Ticke ... ... er upstream/main ...\> git fetch upstream ...\> 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 els ... tinuing 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. Run the following, replacing PRNumber and TicketNumber with the actual pull request and ... ticket numbers: / $ git fetch upstream pull/PRNumber/head:ticket_TicketNumber $ git checkout ticket_TicketNumber $ git push origin ticket_TicketNumber ...\> git fetch upstream pull/PRNumber/head:ticket_TicketNumber ...\> git checkout ticket_Ticke ... ... git commit -m 'Added two more tests for edge cases.' Publishing work ¶ You can publish your work on GitHub by running: git push origin ticket_xxxxx When you go to your GitHub page, you will notice a new branch has been created. If you are working on ... e message. See コミットガイドライン for the required commit message format. After rewriting a commit that has already been pushed to GitHub, you will need to force-push your branch: git push --force-with-lease origin ticket_xxxxx Rebasing branches ¶ ... eady published at GitHub, for example if you're making minor changes to take into account a review, you will need to force-push the changes: git push --force-with-lease origin ticket_xxxxx Note that this will rewrite history of ticket_xxxxx - if you ... ... git commit -m 'Added two more tests for edge cases.' Publishing work ¶ You can publish your work on GitHub by running: git push origin ticket_xxxxx When you go to your GitHub page, you will notice a new branch has been created. If you are working on ... e message. See コミットガイドライン for the required commit message format. After rewriting a commit that has already been pushed to GitHub, you will need to force-push your branch: git push --force-with-lease origin ticket_xxxxx Rebasing branches ¶ ... eady published at GitHub, for example if you're making minor changes to take into account a review, you will need to force-push the changes: git push --force-with-lease origin ticket_xxxxx Note that this will rewrite history of ticket_xxxxx - if you ... ... e --ff-only pr/XXXX $ # If you're not sure if you did things correctly, check that only the $ # changes you expect will be pushed to upstream. $ git push --dry-run upstream main $ # Push! $ git push upstream main $ # Delete the pull request branch. $ ... pr/XXXX ...\> REM If you're not sure if you did things correctly, check that only the ...\> REM changes you expect will be pushed to upstream. ...\> git push --dry-run upstream main ...\> REM Push! ...\> git push upstream main ...\> REM Delete the pu ... ミットを取り消すことができます。 誤ってトピックブランチを django/django にプッシュした場合は、削除してください。例えば、 git push upstream feature_antigravity を実行した場合は、逆のプッシュを行ってください: git push upstream :feature_antigravity 。 目次 ... ... e --ff-only pr/XXXX $ # If you're not sure if you did things correctly, check that only the $ # changes you expect will be pushed to upstream. $ git push --dry-run upstream main $ # Push! $ git push upstream main $ # Delete the pull request branch. $ ... pr/XXXX ...\> REM If you're not sure if you did things correctly, check that only the ...\> REM changes you expect will be pushed to upstream. ...\> git push --dry-run upstream main ...\> REM Push! ...\> git push upstream main ...\> REM Delete the pu ... ミットを取り消すことができます。 誤ってトピックブランチを django/django にプッシュした場合は、削除してください。例えば、 git push upstream feature_antigravity を実行した場合は、逆のプッシュを行ってください: git push upstream :feature_antigravity 。 目次 ... ... -translations repository. For example, when releasing Django 4.2: $ git checkout -b stable/4.2.x origin/stable/4.1.x $ git push origin stable/4.2.x:stable/4.2.x Write the announcement blog post for the release. You can enter it into the admin at any ... st. For example, when feature freezing Django 5.2: $ git fetch upstream $ git checkout -b stable/5.2.x upstream/main $ git push upstream -u stable/5.2.x:stable/5.2.x At the same time, update the django_next_version variable in docs/conf.py on the sta ... ). This will be merged after the final release. Actually rolling the release ¶ OK, this is the fun part, where we actually push out a release! If you're issuing multiple releases , repeat these steps for each release. Check Jenkins is green for the v ... ... れば、その値を返します。そうでない場合は、 default の値を持つ key を挿入し、 default を返します。 Context. pop () ¶ Context. push () ¶ exception ContextPopException [ソース] ¶ コンテキストオブジェクトはスタックです。つまり、 push() したり pop() したりす ... () しすぎると django.template.ContextPopException が発生します: >>> c = Context () >>> c [ "foo" ] = "first level" >>> c . push () {} >>> c [ "foo" ] = "second level" >>> c [ "foo" ] 'second level' >>> c . pop () {'foo': 'second level'} >>> c [ "foo" ... 'overwritten' >>> c . pop () Traceback (most recent call last): ... ContextPopException また、コンテキストマネージャとして push() を使うことで、それに対応する pop() が呼び出されるようにすることもできます。 >>> c = Context () >>> c [ "foo" ] = "first ... ... -translations repository. For example, when releasing Django 4.2: $ git checkout -b stable/4.2.x origin/stable/4.1.x $ git push origin stable/4.2.x:stable/4.2.x Write the announcement blog post for the release. You can enter it into the admin at any ... st. For example, when feature freezing Django 5.2: $ git fetch upstream $ git checkout -b stable/5.2.x upstream/main $ git push upstream -u stable/5.2.x:stable/5.2.x At the same time, update the django_next_version variable in docs/conf.py on the sta ... ). This will be merged after the final release. Actually rolling the release ¶ OK, this is the fun part, where we actually push out a release! If you're issuing multiple releases , repeat these steps for each release. Check Jenkins is green for the v ... ... れば、その値を返します。そうでない場合は、 default の値を持つ key を挿入し、 default を返します。 Context. pop () ¶ Context. push () ¶ exception ContextPopException [ソース] ¶ コンテキストオブジェクトはスタックです。つまり、 push() したり pop() したりす ... () しすぎると django.template.ContextPopException が発生します: >>> c = Context () >>> c [ "foo" ] = "first level" >>> c . push () {} >>> c [ "foo" ] = "second level" >>> c [ "foo" ] 'second level' >>> c . pop () {'foo': 'second level'} >>> c [ "foo" ... 'overwritten' >>> c . pop () Traceback (most recent call last): ... ContextPopException また、コンテキストマネージャとして push() を使うことで、それに対応する pop() が呼び出されるようにすることもできます。 >>> c = Context () >>> c [ "foo" ] = "first ... 2026年10月08日