per page, with , order by , clip by
Results of 1 - 10 of about 14 for pick (0.003 sec.)
Working with Git and GitHub — Django 6.1 ドキュメント 12043
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 ... the last three commits: git rebase -i HEAD~3 This opens an editor listing the three commits, each prefixed with the word "pick". Change "pick" to "reword" (or "r") on the line of the commit you want to change, then save and close. A new editor will ... s shorthand for two latest commits. The above command will open an editor showing the two commits, prefixed with the word "pick". Change "pick" on the second line to "squash" instead. This will keep the first commit, and squash the second commit into ... se. This way you can change a single commit, for example to fix a typo in a docstring: git rebase -i HEAD~3 # Choose edit, pick, pick for the commits # Now you are able to rework the commit (use git add normally to add changes) # When finished, commi ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
コードのコミット — Django 6.1 ドキュメント 11465
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 コミットガイ ... ports to stable branches are done exclusively by mergers, following the サポートバージョン . A backport consists of cherry-picking a commit from main onto the target stable/A.B.x branch. A backport commit must include two things beyond the original c ... 73b1acb07a57d3f806e93928. There are three ways to do a backport, depending on your workflow: Option 1: fully manual Cherry-pick the commit onto the stable branch, then amend the commit message to add the required prefix and backport note: git cherry- ... pick <sha> git commit --amend If the cherry-pick produces conflicts, resolve them, stage the changes, then run git cherry-pick --continue before amending. This option requ ...
https://man.mtool.work/django/6.1/internals/contributing/committing-code.html
Working with Git and GitHub — Django 6.1 ドキュメント 11308
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 ... the last three commits: git rebase -i HEAD~3 This opens an editor listing the three commits, each prefixed with the word "pick". Change "pick" to "reword" (or "r") on the line of the commit you want to change, then save and close. A new editor will ... s shorthand for two latest commits. The above command will open an editor showing the two commits, prefixed with the word "pick". Change "pick" on the second line to "squash" instead. This will keep the first commit, and squash the second commit into ... se. This way you can change a single commit, for example to fix a typo in a docstring: git rebase -i HEAD~3 # Choose edit, pick, pick for the commits # Now you are able to rework the commit (use git add normally to add changes) # When finished, commi ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
コードのコミット — Django 6.1 ドキュメント 10888
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 コミットガイ ... ports to stable branches are done exclusively by mergers, following the サポートバージョン . A backport consists of cherry-picking a commit from main onto the target stable/A.B.x branch. A backport commit must include two things beyond the original c ... 73b1acb07a57d3f806e93928. There are three ways to do a backport, depending on your workflow: Option 1: fully manual Cherry-pick the commit onto the stable branch, then amend the commit message to add the required prefix and backport note: git cherry- ... pick <sha> git commit --amend If the cherry-pick produces conflicts, resolve them, stage the changes, then run git cherry-pick --continue before amending. This option requ ...
https://man.mtool.work/django/6.1/internals/contributing/committing-code.html
新しいコントリビューターへのアドバイス — Django 6.1 ドキュメント 8419
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » 新しいコントリビューターへのアドバイス ¶ 新しいコントリビューターで、何をするべきかわかりませんか? 助けたいと思っているのにどこから手を付ければいいの ... ションを経験しがちです。ここでは、Django での作業をより便利でやりがいのあるものにするためのアドバイスをいくつか紹介します。 Pick a subject area ¶ This should be something that you care about, that you are familiar with or that you want to learn about. ... ポートが不足している可能性があります。 Start small ¶ 大きな問題よりも小さな問題の方がフィードバックを得やすいものです。 easy pickings をチェックしてみてください。 Confirm support before engaging in a big task ¶ つまり、問題を修正する前にバグが本物である ... accepted tickets Keep old patches up-to-date Write some documentation Sign the Contributor License Agreement ガイドライン Pick a subject area Analyze tickets' context and history Start small Confirm support before engaging in a big task Be bold! Lea ...
https://man.mtool.work/django/6.1/internals/contributing/new-contributors.html
新しいコントリビューターへのアドバイス — Django 6.1 ドキュメント 8419
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » 新しいコントリビューターへのアドバイス ¶ 新しいコントリビューターで、何をするべきかわかりませんか? 助けたいと思っているのにどこから手を付ければいいの ... ションを経験しがちです。ここでは、Django での作業をより便利でやりがいのあるものにするためのアドバイスをいくつか紹介します。 Pick a subject area ¶ This should be something that you care about, that you are familiar with or that you want to learn about. ... ポートが不足している可能性があります。 Start small ¶ 大きな問題よりも小さな問題の方がフィードバックを得やすいものです。 easy pickings をチェックしてみてください。 Confirm support before engaging in a big task ¶ つまり、問題を修正する前にバグが本物である ... accepted tickets Keep old patches up-to-date Write some documentation Sign the Contributor License Agreement ガイドライン Pick a subject area Analyze tickets' context and history Start small Confirm support before engaging in a big task Be bold! Lea ...
https://man.mtool.work/django/6.1/internals/contributing/new-contributors.html
チケットをトリアージする — Django 6.1 ドキュメント 7842
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » チケットをトリアージする ¶ Django uses Trac for managing the work on the code base. Trac is a community-tended garden of the bugs people have found ... 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 in the end, we all benefit together. 他のガーデン同様に、我々も完 ... patch no longer applies cleanly, there is a flaw in the implementation, or that the code doesn't meet our standards. Easy pickings (簡単に取り組める) ¶ Tickets that would require small, easy, changes. Type (タイプ) ¶ チケットは以下のいずれかの タイプ ... "Needs tests", "Needs documentation", or "Has patch" flags for tickets where they are incorrectly set. Setting the " Easy pickings " flag for tickets that are small and relatively straightforward. カテゴリーが未設定のチケットに type (タイプ) を設定す ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
チケットをトリアージする — Django 6.1 ドキュメント 7842
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » チケットをトリアージする ¶ Django uses Trac for managing the work on the code base. Trac is a community-tended garden of the bugs people have found ... 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 in the end, we all benefit together. 他のガーデン同様に、我々も完 ... patch no longer applies cleanly, there is a flaw in the implementation, or that the code doesn't meet our standards. Easy pickings (簡単に取り組める) ¶ Tickets that would require small, easy, changes. Type (タイプ) ¶ チケットは以下のいずれかの タイプ ... "Needs tests", "Needs documentation", or "Has patch" flags for tickets where they are incorrectly set. Setting the " Easy pickings " flag for tickets that are small and relatively straightforward. カテゴリーが未設定のチケットに type (タイプ) を設定す ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
マイグレーション — Django 6.1 ドキュメント 7562
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » マイグレーション ¶ マイグレーション (Migrations) は、Django でモデルに対して行った変更 (フィールドの追加やモデルの削除など) をデータベーススキーマに ... ns) will be removed in Django 1.9." ), "hint" : "Use GenericIPAddressField instead." , # optional "id" : "fields.W900" , # pick a unique ID for your field. } あなたが選んだ非推奨期間 (Django 自体のフィールドでは 2、3 回の機能リリース) が経過したら、 ... cept for support in " "historical migrations." ), "hint" : "Use GenericIPAddressField instead." , "id" : "fields.E900" , # pick a unique ID for your field. } __init__() 、 deconstruct() 、 get_internal_type() などのデータベースマイグレーションで動作す ...
https://man.mtool.work/django/6.1/topics/migrations.html
マイグレーション — Django 6.1 ドキュメント 7562
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » マイグレーション ¶ マイグレーション (Migrations) は、Django でモデルに対して行った変更 (フィールドの追加やモデルの削除など) をデータベーススキーマに ... ns) will be removed in Django 1.9." ), "hint" : "Use GenericIPAddressField instead." , # optional "id" : "fields.W900" , # pick a unique ID for your field. } あなたが選んだ非推奨期間 (Django 自体のフィールドでは 2、3 回の機能リリース) が経過したら、 ... cept for support in " "historical migrations." ), "hint" : "Use GenericIPAddressField instead." , "id" : "fields.E900" , # pick a unique ID for your field. } __init__() 、 deconstruct() 、 get_internal_type() などのデータベースマイグレーションで動作す ...
https://man.mtool.work/django/6.1/topics/migrations.html
PREV 1 2 NEXT