per page, with , order by , clip by
Results of 1 - 10 of about 18 for checkout (0.003 sec.)
Sprint quickstart guide — Django 6.1 ドキュメント 11976
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Sprint quickstart guide ¶ This document explains how to prepare to contribute to Django. It is intended for use during sprints, or by people who are ... create a branch for your work, replacing TicketNumber with the actual Trac ticket number: /  $ git fetch upstream $ git checkout -b ticket_TicketNumber upstream/main ...\> git fetch upstream ...\> git checkout -b ticket_TicketNumber upstream/main When ... h the actual pull request and Trac 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_TicketNumber ...\> git push origin ticket_TicketNumber For example, to continue PR 8000 for ticket 123, run: /  ...
https://man.mtool.work/django/6.1/internals/contributing/sprint-quickstart.html
Sprint quickstart guide — Django 6.1 ドキュメント 11976
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Sprint quickstart guide ¶ This document explains how to prepare to contribute to Django. It is intended for use during sprints, or by people who are ... create a branch for your work, replacing TicketNumber with the actual Trac ticket number: /  $ git fetch upstream $ git checkout -b ticket_TicketNumber upstream/main ...\> git fetch upstream ...\> git checkout -b ticket_TicketNumber upstream/main When ... h the actual pull request and Trac 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_TicketNumber ...\> git push origin ticket_TicketNumber For example, to continue PR 8000 for ticket 123, run: /  ...
https://man.mtool.work/django/6.1/internals/contributing/sprint-quickstart.html
コードのコミット — Django 6.1 ドキュメント 10380
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » コードのコミット ¶ This section is addressed to the mergers and to anyone interested in knowing how code gets committed into Django. The コミットガイ ... が多くなったら、この git エイリアスが役立つでしょう: [alias] pr = !sh -c \"git fetch upstream pull/${1}/head:pr/${1} && git checkout pr/${1}\" これを ~/.gitconfig に追加し、 upstream を django/django に設定してください。そして、 git pr #### を実行すると、 ... 通りのものであることを確認しましょう。準備ができたら次のようにします: /  $ # Pull in the latest changes from main. $ git checkout main $ git pull upstream main $ # Rebase the pull request on main. $ git checkout pr/#### $ git rebase main $ git checkout ... main $ # Delete the pull request branch. $ git branch -d pr/xxxx ...\> REM Pull in the latest changes from main. ...\> git checkout main ...\> git pull upstream main ...\> REM Rebase the pull request on main. ...\> git checkout pr/#### ...\> git rebase m ...
https://man.mtool.work/django/6.1/internals/contributing/committing-code.html
コードのコミット — Django 6.1 ドキュメント 10380
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » コードのコミット ¶ This section is addressed to the mergers and to anyone interested in knowing how code gets committed into Django. The コミットガイ ... が多くなったら、この git エイリアスが役立つでしょう: [alias] pr = !sh -c \"git fetch upstream pull/${1}/head:pr/${1} && git checkout pr/${1}\" これを ~/.gitconfig に追加し、 upstream を django/django に設定してください。そして、 git pr #### を実行すると、 ... 通りのものであることを確認しましょう。準備ができたら次のようにします: /  $ # Pull in the latest changes from main. $ git checkout main $ git pull upstream main $ # Rebase the pull request on main. $ git checkout pr/#### $ git rebase main $ git checkout ... main $ # Delete the pull request branch. $ git branch -d pr/xxxx ...\> REM Pull in the latest changes from main. ...\> git checkout main ...\> git pull upstream main ...\> REM Rebase the pull request on main. ...\> git checkout pr/#### ...\> git rebase m ...
https://man.mtool.work/django/6.1/internals/contributing/committing-code.html
How to release Django — Django 6.1 ドキュメント 10260
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up How to release Django ¶ このドキュメントでは、Django のリリース方法について説明しています。 これらの手順を変更した場合は、最新の情報を保ってください! ここでの ... h from the current stable branch in the django-docs-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 r ... Be sure to fetch and update upstream to latest. 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_ve ... ase always begins from a release branch, so you should make sure you're on an up-to-date stable branch. For example: $ git checkout stable/4.1.x $ git pull If this is a security release, merge the appropriate patches from django-security . Rebase these p ...
https://man.mtool.work/django/6.1/internals/howto-release-django.html
How to release Django — Django 6.1 ドキュメント 10123
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up How to release Django ¶ このドキュメントでは、Django のリリース方法について説明しています。 これらの手順を変更した場合は、最新の情報を保ってください! ここでの ... h from the current stable branch in the django-docs-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 r ... Be sure to fetch and update upstream to latest. 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_ve ... ase always begins from a release branch, so you should make sure you're on an up-to-date stable branch. For example: $ git checkout stable/4.1.x $ git pull If this is a security release, merge the appropriate patches from django-security . Rebase these p ...
https://man.mtool.work/django/6.1/internals/howto-release-django.html
Working with Git and GitHub — Django 6.1 ドキュメント 8407
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Working with Git and GitHub ¶ This section explains how the community can contribute code to Django via pull requests. If you're interested in how m ... orking on a ticket ¶ When working on a ticket, create a new branch for the work, and base that work on upstream/main : git checkout -b ticket_xxxxx upstream/main The -b flag creates a new branch for you locally. Don't hesitate to create new branches even ... allest things - that's what they are there for. If instead you were working for a fix on the 1.4 branch, you would do: git checkout -b ticket_xxxxx_1_4 upstream/stable/1.4.x Assume the work is carried on the ticket_xxxxx branch. Make some changes and com ... Those patches will typically exist as pull requests on GitHub and can be easily integrated into your local repository: git checkout -b pull_xxxxx upstream/main curl -L https://github.com/django/django/pull/xxxxx.patch | git am This will create a new bran ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
Working with Git and GitHub — Django 6.1 ドキュメント 8407
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Working with Git and GitHub ¶ This section explains how the community can contribute code to Django via pull requests. If you're interested in how m ... orking on a ticket ¶ When working on a ticket, create a new branch for the work, and base that work on upstream/main : git checkout -b ticket_xxxxx upstream/main The -b flag creates a new branch for you locally. Don't hesitate to create new branches even ... allest things - that's what they are there for. If instead you were working for a fix on the 1.4 branch, you would do: git checkout -b ticket_xxxxx_1_4 upstream/stable/1.4.x Assume the work is carried on the ticket_xxxxx branch. Make some changes and com ... Those patches will typically exist as pull requests on GitHub and can be easily integrated into your local repository: git checkout -b pull_xxxxx upstream/main curl -L https://github.com/django/django/pull/xxxxx.patch | git am This will create a new bran ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
JavaScript code — Django 6.1 ドキュメント 7549
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » JavaScript code ¶ While most of Django core is Python, the admin and gis contrib apps contain JavaScript code. Please follow these coding standards ... After installing Node.js , install the JavaScript test dependencies by running the following from the root of your Django checkout: /  $ npm install ...\> npm install Then run the tests with: /  $ npm test ...\> npm test 目次 JavaScript code Code ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/javascript...
JavaScript code — Django 6.1 ドキュメント 7429
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » JavaScript code ¶ While most of Django core is Python, the admin and gis contrib apps contain JavaScript code. Please follow these coding standards ... After installing Node.js , install the JavaScript test dependencies by running the following from the root of your Django checkout: /  $ npm install ...\> npm install Then run the tests with: /  $ npm test ...\> npm test 目次 JavaScript code Code ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/javascript...
PREV 1 2 NEXT