Results of 1 - 8 of about 8 for Merger (0.017 sec.)
- Organization of the Django Project — Django 4.0.6 ドキュメント 13664
- " + tagname + " "); } }); $("div.highlight\\-html\\+django span.nf").each(function(i, elem) { va
... Django framework, its ecosystem and its community. Mergers ¶ Role ¶ Mergers are a small set of people who me ... ests to the Django Git repository . Prerogatives ¶ Mergers hold the following prerogatives: Merging any pull ... ugh not to require the use of the DEP process ). A Merger must not merge a change primarily authored by that ... Merger, unless the pull request has been approved by: ano ...
-
https://man.plustar.jp/django/internals/organization.html
- [similar]
- Working with Git and GitHub — Django 4.0.6 ドキュメント 9254
- " + tagname + " "); } }); $("div.highlight\\-html\\+django span.nf").each(function(i, elem) { va
... ngo via pull requests. If you're interested in how mergers handle them, see コードのコミット . Below, we are ... commit message guidelines to ease the work of the merger. If you're uncomfortable with English, try at leas ... GitHub have only two states: open and closed. The merger who will deal with your pull request has only two ... ready for merging -- or sufficiently close that a merger will finish it themselves. Rebasing branches ¶ In ...
-
https://man.plustar.jp/django/internals/contributing/writing-code/working-with-g...
- [similar]
- コードのコミット — Django 4.0.6 ドキュメント 8874
- " + tagname + " "); } }); $("div.highlight\\-html\\+django span.nf").each(function(i, elem) { va
... コードのコミット ¶ This section is addressed to the mergers and to anyone interested in knowing how code gets ... best pull requests possible. In practice however, mergers - who will likely be more familiar with the commi ... se. Practicality beats purity, so it is up to each merger to decide how much history mangling to do for a pu ... ble-check your work, or have it checked by another merger, before you commit it in the first place! When a m ...
-
https://man.plustar.jp/django/internals/contributing/committing-code.html
- [similar]
- Triaging tickets — Django 4.0.6 ドキュメント 8332
- " + tagname + " "); } }); $("div.highlight\\-html\\+django span.nf").each(function(i, elem) { va
... start there: We've got two roles in this diagram: Mergers: people with commit access who are responsible fo ... marks the ticket as "Ready for checkin". Jacob, a merger , reviews the pull request and merges it. Some tic ... t all the requirements for a commit-ready patch. A merger now needs to give the patch a final review prior t ...
-
https://man.plustar.jp/django/internals/contributing/triaging-tickets.html
- [similar]
- Submitting patches — Django 4.0.6 ドキュメント 8097
- " + tagname + " "); } }); $("div.highlight\\-html\\+django span.nf").each(function(i, elem) { va
... nd/or "Needs tests". As time and interest permits, mergers do final reviews of "Ready for checkin" tickets a ... rks need to be done. If you're looking to become a merger, doing thorough reviews of patches is a great way ...
-
https://man.plustar.jp/django/internals/contributing/writing-code/submitting-pat...
- [similar]
- Coding style — Django 4.0.6 ドキュメント 8025
- " + tagname + " "); } }); $("div.highlight\\-html\\+django span.nf").each(function(i, elem) { va
... ty. Final judgments of readability are left to the Merger's discretion. As a guide, f-strings should use onl ...
-
https://man.plustar.jp/django/internals/contributing/writing-code/coding-style.h...
- [similar]
- Writing documentation — Django 4.0.6 ドキュメント 8025
- " + tagname + " "); } }); $("div.highlight\\-html\\+django span.nf").each(function(i, elem) { va
... n fixes and improvements, at the discretion of the merger, to the last release branch. That's because it's h ...
-
https://man.plustar.jp/django/internals/contributing/writing-documentation.html
- [similar]
- 次のステップへ — Django 4.0.6 ドキュメント 7952
- " + tagname + " "); } }); $("div.highlight\\-html\\+django span.nf").each(function(i, elem) { va
... the last release branch, at the discretion of the merger, however, once a version of Django is no longer su ...
-
https://man.plustar.jp/django/intro/whatsnext.html
- [similar]
PREV
1
NEXT