per page, with , order by , clip by
Results of 1 - 10 of about 44 for review (0.004 sec.)
チケットをトリアージする — Django 6.1 ドキュメント 13662
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 ... the tracker organized. Bug fixers: anyone can contribute by opening a pull request and working on a solution for a ticket. Reviewers: anyone can review pull requests and suggest improvements. Mergers: people with commit access who make the final decisi ... and GitHub repositories are intentionally open to the public. Anyone can help by working on tickets, triaging tickets and reviewing changes. Django is a community project, and we encourage triage and collaboration by the community . We truly want you ... le of a ticket: Alice creates a ticket and opens an incomplete pull request (missing tests, incorrect implementation). Bob reviews the pull request, marks the ticket as "Accepted", sets the flags "needs tests" and "patch needs improvement", and leaves ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
チケットをトリアージする — Django 6.1 ドキュメント 13355
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 ... the tracker organized. Bug fixers: anyone can contribute by opening a pull request and working on a solution for a ticket. Reviewers: anyone can review pull requests and suggest improvements. Mergers: people with commit access who make the final decisi ... and GitHub repositories are intentionally open to the public. Anyone can help by working on tickets, triaging tickets and reviewing changes. Django is a community project, and we encourage triage and collaboration by the community . We truly want you ... le of a ticket: Alice creates a ticket and opens an incomplete pull request (missing tests, incorrect implementation). Bob reviews the pull request, marks the ticket as "Accepted", sets the flags "needs tests" and "patch needs improvement", and leaves ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
Submitting contributions — Django 6.1 ドキュメント 11049
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Submitting contributions ¶ We're always grateful for contributions to Django's code. Indeed, bug reports with associated contributions will get fixe ... the behavior of an existing feature, the change should also contain documentation. When you think your work is ready to be reviewed, send a GitHub pull request . If you can't send a pull request for some reason, you can also use patches in Trac. When u ... ", "Needs tests", and "Patch needs improvement" boxes aren't checked. This makes the ticket appear in the "Patches needing review" queue on the Development dashboard . AI-Assisted Contributions ¶ Unverified AI-generated contributions create unnecessary ... e burden and slow down meaningful progress. Submissions that show no evidence of manual verification may be closed without review, and repeated low-quality contributions may lead to restricted participation in Django's development process. With the wid ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
Submitting contributions — Django 6.1 ドキュメント 10665
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Submitting contributions ¶ We're always grateful for contributions to Django's code. Indeed, bug reports with associated contributions will get fixe ... the behavior of an existing feature, the change should also contain documentation. When you think your work is ready to be reviewed, send a GitHub pull request . If you can't send a pull request for some reason, you can also use patches in Trac. When u ... ", "Needs tests", and "Patch needs improvement" boxes aren't checked. This makes the ticket appear in the "Patches needing review" queue on the Development dashboard . AI-Assisted Contributions ¶ Unverified AI-generated contributions create unnecessary ... e burden and slow down meaningful progress. Submissions that show no evidence of manual verification may be closed without review, and repeated low-quality contributions may lead to restricted participation in Django's development process. With the wid ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
Working with Git and GitHub — Django 6.1 ドキュメント 8590
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 ... tHub pull request containing the changes for Trac ticket #xxxxx. By creating a fully-ready pull request, you will make the reviewer's job easier, meaning that your work is more likely to be merged into Django. You could also upload a traditional patch ... to Trac, but it's less practical for reviews. Git のインストール ¶ Django uses Git for its source control. You can download Git, but it's often easier to install with ... ed. If your topic branch is already 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 hist ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
Working with Git and GitHub — Django 6.1 ドキュメント 8590
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 ... tHub pull request containing the changes for Trac ticket #xxxxx. By creating a fully-ready pull request, you will make the reviewer's job easier, meaning that your work is more likely to be merged into Django. You could also upload a traditional patch ... to Trac, but it's less practical for reviews. Git のインストール ¶ Django uses Git for its source control. You can download Git, but it's often easier to install with ... ed. If your topic branch is already 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 hist ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
バグレポートと機能のリクエスト — Django 6.1 ドキュメント 7745
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » バグレポートと機能のリクエスト ¶ 重要 Please report security issues only to security@djangoproject.com . This is a private list only open to long-ti ... n on this feature ?: This feature seems like a straightforward and beneficial addition The Steering Council will regularly review the ideas in the project, moving those with community support through the following stages: アイデア Approved - Idea refin ... ement - Team creation 進行中 Working solution - Review - Feedback Needs maintainer (Django only) 完了 Occasionally, discussions on feature ideas or the direction of Django may t ... 更新 guide for instructions on getting up to date. To ensure your project is ready, you should also: Read the release notes: Review the リリースノート for the upcoming version to learn about upgrade paths for deprecated features or about minor backward-i ...
https://man.mtool.work/django/6.1/internals/contributing/bugs-and-features.html
Coding style — Django 6.1 ドキュメント 7745
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 code review it allows the reviewer to focus on the change itself, and it can also hel ... te error message will be displayed. If the error was with black or isort then the tool will go ahead and fix them for you. Review the changes and re-stage for commit if you are happy with them. Python style ¶ All files should be formatted using the bla ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/coding-sty...
バグレポートと機能のリクエスト — Django 6.1 ドキュメント 7745
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » バグレポートと機能のリクエスト ¶ 重要 Please report security issues only to security@djangoproject.com . This is a private list only open to long-ti ... n on this feature ?: This feature seems like a straightforward and beneficial addition The Steering Council will regularly review the ideas in the project, moving those with community support through the following stages: アイデア Approved - Idea refin ... ement - Team creation 進行中 Working solution - Review - Feedback Needs maintainer (Django only) 完了 Occasionally, discussions on feature ideas or the direction of Django may t ... 更新 guide for instructions on getting up to date. To ensure your project is ready, you should also: Read the release notes: Review the リリースノート for the upcoming version to learn about upgrade paths for deprecated features or about minor backward-i ...
https://man.mtool.work/django/6.1/internals/contributing/bugs-and-features.html
Coding style — Django 6.1 ドキュメント 7745
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 code review it allows the reviewer to focus on the change itself, and it can also hel ... te error message will be displayed. If the error was with black or isort then the tool will go ahead and fix them for you. Review the changes and re-stage for commit if you are happy with them. Python style ¶ All files should be formatted using the bla ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/coding-sty...
PREV 1 2 3 4 5 NEXT