per page, with , order by , clip by
Results of 1 - 10 of about 10 for repo (0.006 sec.)
Unit tests — Django 6.1 ドキュメント 12925
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Unit tests ¶ Django comes with a test suite of its own, in the tests directory of the code base. It's our policy to make sure all tests pass at all ... fork, install some requirements, and run the tests: /  $ git clone https://github.com/YourGitHubName/django.git django-repo $ cd django-repo/tests $ python -m pip install -e .. $ python -m pip install -r requirements/py3.txt $ ./runtests.py ...\> ... git clone https://github.com/YourGitHubName/django.git django-repo ...\> cd django-repo\tests ...\> py -m pip install -e .. ...\> py -m pip install -r requirements\py3.txt ...\> runtests.py ... , combine all coverage statistics by running: /  $ coverage combine ...\> coverage combine After that generate the html report by running: /  $ coverage html ...\> coverage html When running coverage for the Django tests, the included .coverage ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/unit-tests...
Unit tests — Django 6.1 ドキュメント 11584
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Unit tests ¶ Django comes with a test suite of its own, in the tests directory of the code base. It's our policy to make sure all tests pass at all ... fork, install some requirements, and run the tests: /  $ git clone https://github.com/YourGitHubName/django.git django-repo $ cd django-repo/tests $ python -m pip install -e .. $ python -m pip install -r requirements/py3.txt $ ./runtests.py ...\> ... git clone https://github.com/YourGitHubName/django.git django-repo ...\> cd django-repo\tests ...\> py -m pip install -e .. ...\> py -m pip install -r requirements\py3.txt ...\> runtests.py ... , combine all coverage statistics by running: /  $ coverage combine ...\> coverage combine After that generate the html report by running: /  $ coverage html ...\> coverage html When running coverage for the Django tests, the included .coverage ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/unit-tests...
How to release Django — Django 6.1 ドキュメント 8867
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up How to release Django ¶ このドキュメントでは、Django のリリース方法について説明しています。 これらの手順を変更した場合は、最新の情報を保ってください! ここでの ... pypi django [pypi] username = __token__ password = # User-scoped or project-scoped token, to set as the default. [django] repository = https://upload.pypi.org/legacy/ username = __token__ password = # A project token. Access to Django's project on T ... jango Forum - Announcements category and to send emails to the django-announce mailing list. Access to the django-security repo in GitHub. Among other things, this provides access to the pre-notification distribution list (needed for security release ... m/en/dev/internals/security/#how-django-discloses-security-issues Prepare issue metadata: * Severity * Short description * Reporter * Remediator * Reported at * Confirmed at (usually date CVE reserved) * CWE Problem Type * CAPEC Impact Type * CVSS (4 ...
https://man.mtool.work/django/6.1/internals/howto-release-django.html
How to release Django — Django 6.1 ドキュメント 8867
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up How to release Django ¶ このドキュメントでは、Django のリリース方法について説明しています。 これらの手順を変更した場合は、最新の情報を保ってください! ここでの ... pypi django [pypi] username = __token__ password = # User-scoped or project-scoped token, to set as the default. [django] repository = https://upload.pypi.org/legacy/ username = __token__ password = # A project token. Access to Django's project on T ... jango Forum - Announcements category and to send emails to the django-announce mailing list. Access to the django-security repo in GitHub. Among other things, this provides access to the pre-notification distribution list (needed for security release ... m/en/dev/internals/security/#how-django-discloses-security-issues Prepare issue metadata: * Severity * Short description * Reporter * Remediator * Reported at * Confirmed at (usually date CVE reserved) * CWE Problem Type * CAPEC Impact Type * CVSS (4 ...
https://man.mtool.work/django/6.1/internals/howto-release-django.html
Working with Git and GitHub — Django 6.1 ドキュメント 8527
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 ... control. You can download Git, but it's often easier to install with your operating system's package manager. Django's Git repository is hosted on GitHub , and it is recommended that you also work using GitHub. After installing Git, the first thing y ... you use in the user.email field, as this will be used to associate your commits with your GitHub account. Setting up local repository ¶ When you have created your GitHub account, with the nick "GitHub_nick", and forked Django's repository , create a ... one https://github.com/GitHub_nick/django.git This will create a new directory "django", containing a clone of your GitHub repository. The rest of the git commands on this page need to be run within the cloned directory, so switch to it now: cd djang ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
Working with Git and GitHub — Django 6.1 ドキュメント 8527
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 ... control. You can download Git, but it's often easier to install with your operating system's package manager. Django's Git repository is hosted on GitHub , and it is recommended that you also work using GitHub. After installing Git, the first thing y ... you use in the user.email field, as this will be used to associate your commits with your GitHub account. Setting up local repository ¶ When you have created your GitHub account, with the nick "GitHub_nick", and forked Django's repository , create a ... one https://github.com/GitHub_nick/django.git This will create a new directory "django", containing a clone of your GitHub repository. The rest of the git commands on this page need to be run within the cloned directory, so switch to it now: cd djang ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
コードのコミット — Django 6.1 ドキュメント 7848
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 コミットガイ ... こと、そして使えるコミット履歴を持つことです。 コミットガイドライン ¶ These guidelines apply to all commits to Django's Git repository, whether submitted by a contributor via a pull request or landed directly by a merger: 強制プッシュによって django/d ... d provide the context and reasoning that the code cannot. Credit the contributors in the commit message: "Thanks A for the report and B for review." Use git's Co-Authored-By as appropriate, including anyone whose earlier work the change builds on. 例 ... guidelines of how to use Git, GitHub, and how to use pull request together with Trac instead. Thanks to Full Name for the report, and to Reviewer for reviews. コミットは、意味のある最も細かい変更に限定しましょう。つまり、大きなコミットをたまに行うの ...
https://man.mtool.work/django/6.1/internals/contributing/committing-code.html
コードのコミット — Django 6.1 ドキュメント 7848
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 コミットガイ ... こと、そして使えるコミット履歴を持つことです。 コミットガイドライン ¶ These guidelines apply to all commits to Django's Git repository, whether submitted by a contributor via a pull request or landed directly by a merger: 強制プッシュによって django/d ... d provide the context and reasoning that the code cannot. Credit the contributors in the commit message: "Thanks A for the report and B for review." Use git's Co-Authored-By as appropriate, including anyone whose earlier work the change builds on. 例 ... guidelines of how to use Git, GitHub, and how to use pull request together with Trac instead. Thanks to Full Name for the report, and to Reviewer for reviews. コミットは、意味のある最も細かい変更に限定しましょう。つまり、大きなコミットをたまに行うの ...
https://man.mtool.work/django/6.1/internals/contributing/committing-code.html
django-admin と manage.py — Django 6.1 ドキュメント 7168
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » django-admin と manage.py ¶ django-admin は Django の管理タスクのためのコマンドラインユーティリティです。このドキュメントでは、その機能の全体を一通り ... atic creation of the destination directory was added. 例: django-admin startproject myproject /Users/jezdez/Code/myproject_repo --template TEMPLATE ¶ ディレクトリ、ファイルパス、またはカスタムプロジェクトテンプレートの URL を指定します。使用例について ...
https://man.mtool.work/django/6.1/ref/django-admin.html
django-admin と manage.py — Django 6.1 ドキュメント 7168
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » django-admin と manage.py ¶ django-admin は Django の管理タスクのためのコマンドラインユーティリティです。このドキュメントでは、その機能の全体を一通り ... atic creation of the destination directory was added. 例: django-admin startproject myproject /Users/jezdez/Code/myproject_repo --template TEMPLATE ¶ ディレクトリ、ファイルパス、またはカスタムプロジェクトテンプレートの URL を指定します。使用例について ...
https://man.mtool.work/django/6.1/ref/django-admin.html
PREV 1 NEXT