per page, with , order by , clip by
Results of 1 - 10 of about 14 for commits (0.004 sec.)
Working with Git and GitHub — Django 6.1 ドキュメント 13023
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_n ... r example. Other people shouldn't base their work on such a branch, because their clone would become corrupt when you edit commits. There are also "public branches". These are branches other people are supposed to fork, so the history of these branches ... think your work is ready to be pulled into Django, you should create a pull request at GitHub. A good pull request means: commits with one logical change in each, following the coding style , well-formed messages for each commit: a summary line and the ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
Working with Git and GitHub — Django 6.1 ドキュメント 13023
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_n ... r example. Other people shouldn't base their work on such a branch, because their clone would become corrupt when you edit commits. There are also "public branches". These are branches other people are supposed to fork, so the history of these branches ... think your work is ready to be pulled into Django, you should create a pull request at GitHub. A good pull request means: commits with one logical change in each, following the coding style , well-formed messages for each commit: a summary line and the ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
チケットをトリアージする — Django 6.1 ドキュメント 8122
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 ... duced (i.e. a point where the test passes). Use something like git checkout HEAD~100 to check out an earlier revision (100 commits earlier, in this case). Check if the test fails. If so, mark that point as "bad" ( git bisect bad ), then check out an ear ... test_regression You should see git bisect use a binary search to automatically checkout revisions between the good and bad commits until it finds the first "bad" commit where the test fails. Now, report your results on the Trac ticket, and please includ ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
チケットをトリアージする — Django 6.1 ドキュメント 8122
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 ... duced (i.e. a point where the test passes). Use something like git checkout HEAD~100 to check out an earlier revision (100 commits earlier, in this case). Check if the test fails. If so, mark that point as "bad" ( git bisect bad ), then check out an ear ... test_regression You should see git bisect use a binary search to automatically checkout revisions between the good and bad commits until it finds the first "bad" commit where the test fails. Now, report your results on the Trac ticket, and please includ ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
Django 0.96 リリースノート — Django 6.1 ドキュメント 8069
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 0.96 リリースノート ¶ Django 0.96 へようこそ! The primary goal for 0.96 is a cleanup and stabilization of the features introduced in 0.95. Th ... recommend writing a middleware class to activate it. What's new in 0.96? ¶ This revision represents over a thousand source commits and over four hundred bug fixes, so we can't possibly catalog all the changes. Here, we describe the most notable changes ...
https://man.mtool.work/django/6.1/releases/0.96.html
Django 1.0 リリースノート — Django 6.1 ドキュメント 8069
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.0 リリースノート ¶ Django 1.0 へようこそ! We've been looking forward to this moment for over three years, and it's finally here. Django 1.0 ... roject.com/wiki/BackwardsIncompatibleChanges . Django 1.0 の新機能 ¶ A lot ! Since Django 0.96, we've made over 4,000 code commits, fixed more than 2,000 bugs, and edited, added, or removed around 350,000 lines of code. We've also added 40,000 lines of ...
https://man.mtool.work/django/6.1/releases/1.0.html
Django 0.96 リリースノート — Django 6.1 ドキュメント 8069
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 0.96 リリースノート ¶ Django 0.96 へようこそ! The primary goal for 0.96 is a cleanup and stabilization of the features introduced in 0.95. Th ... recommend writing a middleware class to activate it. What's new in 0.96? ¶ This revision represents over a thousand source commits and over four hundred bug fixes, so we can't possibly catalog all the changes. Here, we describe the most notable changes ...
https://man.mtool.work/django/6.1/releases/0.96.html
Django 1.0 リリースノート — Django 6.1 ドキュメント 8069
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.0 リリースノート ¶ Django 1.0 へようこそ! We've been looking forward to this moment for over three years, and it's finally here. Django 1.0 ... roject.com/wiki/BackwardsIncompatibleChanges . Django 1.0 の新機能 ¶ A lot ! Since Django 0.96, we've made over 4,000 code commits, fixed more than 2,000 bugs, and edited, added, or removed around 350,000 lines of code. We've also added 40,000 lines of ...
https://man.mtool.work/django/6.1/releases/1.0.html
Django 1.1 リリースノート — Django 6.1 ドキュメント 8017
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.1 リリースノート ¶ July 29, 2009 Django 1.1 へようこそ! Django 1.1 includes a number of nifty new features , lots of bug fixes, and an easy ... s and strategy, see Django のリリースプロセス . Django 1.1 の新機能 ¶ Quite a bit: since Django 1.0, we've made 1,290 code commits, fixed 1,206 bugs, and added roughly 10,000 lines of documentation. The major new features in Django 1.1 are: ORM improvem ...
https://man.mtool.work/django/6.1/releases/1.1.html
Django 1.1 リリースノート — Django 6.1 ドキュメント 8017
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.1 リリースノート ¶ July 29, 2009 Django 1.1 へようこそ! Django 1.1 includes a number of nifty new features , lots of bug fixes, and an easy ... s and strategy, see Django のリリースプロセス . Django 1.1 の新機能 ¶ Quite a bit: since Django 1.0, we've made 1,290 code commits, fixed 1,206 bugs, and added roughly 10,000 lines of documentation. The major new features in Django 1.1 are: ORM improvem ...
https://man.mtool.work/django/6.1/releases/1.1.html
PREV 1 2 NEXT