per page, with , order by , clip by
Results of 1 - 10 of about 70 for commit (0.008 sec.)
Working with Git and GitHub — Django 6.1 ドキュメント 12237
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 ... not your GitHub nick. GitHub should know the email 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_ ... out -b ticket_xxxxx_1_4 upstream/stable/1.4.x Assume the work is carried on the ticket_xxxxx branch. Make some changes and commit them: git commit When writing the commit message, follow the commit message guidelines to ease the work of the merger. If ... you're uncomfortable with English, try at least to describe precisely what the commit does. If you need to do additional work on your branch, commit as often as necessary: git commit -m 'Added two more tests ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
Working with Git and GitHub — Django 6.1 ドキュメント 12237
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 ... not your GitHub nick. GitHub should know the email 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_ ... out -b ticket_xxxxx_1_4 upstream/stable/1.4.x Assume the work is carried on the ticket_xxxxx branch. Make some changes and commit them: git commit When writing the commit message, follow the commit message guidelines to ease the work of the merger. If ... you're uncomfortable with English, try at least to describe precisely what the commit does. If you need to do additional work on your branch, commit as often as necessary: git commit -m 'Added two more tests ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
コードのコミット — Django 6.1 ドキュメント 10446
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 コミットガイ ... ドライン apply to all contributors, with or without commit rights. If you're a community member who wants to contribute code to Django, look at Working with Git and GitHub instead. ... すると、対応するプルリクエストをチェックアウトできます。 この時点で、コードに手を加えることができます。 git rebase -i と git commit --amend を使って、コミットの品質が期待通りのものであることを確認しましょう。準備ができたら次のようにします: /  $ # Pull ... $ git checkout pr/#### $ git rebase main $ git checkout main $ # Merge the work as "fast-forward" to main to avoid a merge commit. $ # (in practice, you can omit "--ff-only" since you just rebased) $ git merge --ff-only pr/XXXX $ # If you're not sure i ...
https://man.mtool.work/django/6.1/internals/contributing/committing-code.html
コードのコミット — Django 6.1 ドキュメント 10446
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 コミットガイ ... ドライン apply to all contributors, with or without commit rights. If you're a community member who wants to contribute code to Django, look at Working with Git and GitHub instead. ... すると、対応するプルリクエストをチェックアウトできます。 この時点で、コードに手を加えることができます。 git rebase -i と git commit --amend を使って、コミットの品質が期待通りのものであることを確認しましょう。準備ができたら次のようにします: /  $ # Pull ... $ git checkout pr/#### $ git rebase main $ git checkout main $ # Merge the work as "fast-forward" to main to avoid a merge commit. $ # (in practice, you can omit "--ff-only" since you just rebased) $ git merge --ff-only pr/XXXX $ # If you're not sure i ...
https://man.mtool.work/django/6.1/internals/contributing/committing-code.html
How to release Django — Django 6.1 ドキュメント 9953
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up How to release Django ¶ このドキュメントでは、Django のリリース方法について説明しています。 これらの手順を変更した場合は、最新の情報を保ってください! ここでの ... n the project admin . This populates a lot of boilerplate you will need for announcements, CVE publication, and hashes for commit messages. By using this app for preparing security issue metadata, your peer releasers can check your entries and consult ... ne the release date of a non-security release if required. Check with the other mergers to make sure they don't have any uncommitted changes for the release. Proofread the release notes, including looking at the online version to catch any broken links ... translations.py fetch -v 1 --since = <some date> To determine a good value for --since , check the date of the most recent commit with wording similar to Updated translations from Transifex and use a date a few days prior. This command takes some time ...
https://man.mtool.work/django/6.1/internals/howto-release-django.html
How to release Django — Django 6.1 ドキュメント 9953
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up How to release Django ¶ このドキュメントでは、Django のリリース方法について説明しています。 これらの手順を変更した場合は、最新の情報を保ってください! ここでの ... n the project admin . This populates a lot of boilerplate you will need for announcements, CVE publication, and hashes for commit messages. By using this app for preparing security issue metadata, your peer releasers can check your entries and consult ... ne the release date of a non-security release if required. Check with the other mergers to make sure they don't have any uncommitted changes for the release. Proofread the release notes, including looking at the online version to catch any broken links ... translations.py fetch -v 1 --since = <some date> To determine a good value for --since , check the date of the most recent commit with wording similar to Updated translations from Transifex and use a date a few days prior. This command takes some time ...
https://man.mtool.work/django/6.1/internals/howto-release-django.html
データベースのトランザクション — Django 6.1 ドキュメント 9346
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » データベースのトランザクション ¶ Django では、データベースのトランザクションをコントロールする方法が提供されています。 データベースのトランザクション ... tuff () and as a context manager : from django.db import transaction def viewfunc ( request ): # This code executes in autocommit mode (Django's default). do_stuff () with transaction . atomic (): # This code executes inside a transaction. do_more_stuf ... を積極的に更新する場合、トランザクションが実際にコミットされるまでキャッシュの改変を延期するために、代わりに transaction.on_commit() を使用することを推奨します。 アトミックを保証するために、 atomic はいくつかの API を無効にします。アトミックな atomic ブ ... ンザクション管理 を無効にすることもできますが、推奨されません。 トランザクション管理を無効化する ¶ データベースの設定で AUTOCOMMIT を False にすると、Django のトランザクション管理を完全に無効にできます。こうすると、 Django は自動コミットを有効にせず、コ ...
https://man.mtool.work/django/6.1/topics/db/transactions.html
データベースのトランザクション — Django 6.1 ドキュメント 9346
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » データベースのトランザクション ¶ Django では、データベースのトランザクションをコントロールする方法が提供されています。 データベースのトランザクション ... tuff () and as a context manager : from django.db import transaction def viewfunc ( request ): # This code executes in autocommit mode (Django's default). do_stuff () with transaction . atomic (): # This code executes inside a transaction. do_more_stuf ... を積極的に更新する場合、トランザクションが実際にコミットされるまでキャッシュの改変を延期するために、代わりに transaction.on_commit() を使用することを推奨します。 アトミックを保証するために、 atomic はいくつかの API を無効にします。アトミックな atomic ブ ... ンザクション管理 を無効にすることもできますが、推奨されません。 トランザクション管理を無効化する ¶ データベースの設定で AUTOCOMMIT を False にすると、Django のトランザクション管理を完全に無効にできます。こうすると、 Django は自動コミットを有効にせず、コ ...
https://man.mtool.work/django/6.1/topics/db/transactions.html
Coding style — Django 6.1 ドキュメント 8853
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Coding style ¶ Please follow these coding standards when writing code for inclusion in Django. Pre-commit checks ¶ pre-commit is a framework for man ... aging pre-commit hooks. These hooks help to identify simple issues before committing code for review. By checking for these issues before c ... er to focus on the change itself, and it can also help to reduce the number of CI runs. To use the tool, first install pre-commit and then the git hooks: /  $ python -m pip install pre-commit $ pre-commit install ...\> py -m pip install pre-commit . ... ..\> pre-commit install On the first commit pre-commit will install the hooks, these are installed in their own environments and will take ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/coding-sty...
Coding style — Django 6.1 ドキュメント 8811
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Coding style ¶ Please follow these coding standards when writing code for inclusion in Django. Pre-commit checks ¶ pre-commit is a framework for man ... aging pre-commit hooks. These hooks help to identify simple issues before committing code for review. By checking for these issues before c ... er to focus on the change itself, and it can also help to reduce the number of CI runs. To use the tool, first install pre-commit and then the git hooks: /  $ python -m pip install pre-commit $ pre-commit install ...\> py -m pip install pre-commit . ... ..\> pre-commit install On the first commit pre-commit will install the hooks, these are installed in their own environments and will take ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/coding-sty...
PREV 1 2 3 4 5 6 7 NEXT