/third_party/typescript/scripts/ |
D | request-pr-review.ts | 39 const reviewers = Array.isArray(options.reviewer) ? options.reviewer : [options.reviewer]; constant 49 reviewers, 52 console.log(`Added ${reviewers.join(", ")} to ${response.data.url}`); 55 console.log(`Failed to add ${reviewers.join(", ")} to the pull request.`);
|
D | open-user-pr.ts | 8 const reviewers = process.env.REQUESTING_USER ? [process.env.REQUESTING_USER] : ["weswigham", "sand… constant 44 cc ${reviewers.map(r => "@" + r).join(" ")}`, 53 reviewers,
|
D | open-cherry-pick-pr.ts | 11 const reviewers = process.env.REQUESTING_USER ? [process.env.REQUESTING_USER] : ["weswigham", "Ryan… constant 96 cc ${reviewers.map(r => "@" + r).join(" ")}`,
|
/third_party/openssl/dev/ |
D | release.sh | 73 reviewers= 133 reviewers="$reviewers $1=$2" 341 if [ -n "$reviewers" ]; then 342 addrev --release --nopr $reviewers 379 if [ -n "$reviewers" ]; then 380 addrev --release --nopr $reviewers 481 if [ -n "$reviewers" ]; then 482 addrev --release --nopr $reviewers 512 if [ -n "$reviewers" ]; then 513 addrev --release --nopr $reviewers [all …]
|
/third_party/flutter/skia/third_party/externals/angle2/doc/ |
D | ContributingCode.md | 76 … * Use `git cl format` to amend the style of your CL. This saves both your time and the reviewers'! 86 …* [Select reviewers](#selecting-reviewers). If you don't do this, reviewers may not realize you'r… 98 ### Selecting reviewers 99 …reviewers. They will be able to route your CL to additional reviewers as neccssary and answer any …
|
D | CodeReviewProcess.md | 3 This page describes the review process for ANGLE reviewers and committers. For 9 The author of a CL may designate reviewers. Please feel free to weigh in on 13 or, if you are one of the designated reviewers, the change will appear in
|
/third_party/skia/third_party/externals/angle2/doc/ |
D | ContributingCode.md | 155 … * Use `git cl format` to amend the style of your CL. This saves both your time and the reviewers'! 165 * [Select reviewers](#selecting-reviewers). If you don't do this, reviewers may not realize 183 ### Selecting reviewers 186 Gerrit to select appropriate code reviewers. They will be able to route your 187 CL to additional reviewers as neccessary and answer any questions you may have 215 button. It is wise to add the author and reviewers of the original CL as reviewers of the revert 234 * Then, apply your fixes, and upload your CL as a new Patchset. The reviewers will be able to see
|
D | CodeReviewProcess.md | 3 This page describes the review process for ANGLE reviewers and committers. For 9 The author of a CL may designate reviewers. Please feel free to weigh in on 13 or, if you are one of the designated reviewers, the change will appear in
|
/third_party/vulkan-loader/ |
D | GOVERNANCE.md | 44 - Approvers can self-assign their reviewers 45 …- For complex or invasive contributions, Project Leads may request approval from specific reviewers
|
/third_party/skia/include/private/ |
D | OWNERS | 1 # include/ has a restricted set of reviewers (to limit changes to public API)
|
/third_party/flutter/skia/third_party/externals/angle2/ |
D | OWNERS | 1 …googlesource.com/angle/angle/+/master/doc/ContributingCode.md#selecting-reviewers for per-file own…
|
/third_party/skia/third_party/externals/dawn/ |
D | OWNERS | 5 # Backup reviewers if needed.
|
/third_party/libsnd/ |
D | CODEOWNERS | 1 # The owners of this repository. In order of suggestions as reviewers.
|
/third_party/skia/include/ |
D | OWNERS | 3 # Include one of the following reviewers for CLs that add or change Skia's public API:
|
/third_party/flutter/flutter/ |
D | CODEOWNERS | 2 # suggested reviewers for contributions to this repository.
|
/third_party/node/tools/ |
D | find-inactive-collaborators.mjs | 55 // Get all approving reviewers of landed commits during the time period. 188 console.log(`* ${approvingReviewers.size.toLocaleString()} reviewers have approved landed commits.`…
|
/third_party/skia/third_party/externals/dawn/docs/ |
D | contributing.md | 84 click on "Start Review", add reviewers and click "Send and start review". If 85 you are unsure which reviewers to use, pick one of the reviewers in the
|
/third_party/skia/third_party/externals/angle2/ |
D | OWNERS | 1 …omium.googlesource.com/angle/angle/+/main/doc/ContributingCode.md#selecting-reviewers for more info
|
/third_party/skia/site/docs/dev/contrib/ |
D | submit.md | 77 appropriate reviewers for your change. The button is located here: 127 Unless you send your change to reviewers, no one will know to look at it. 163 _Note_: As you work through the review process, both you and your reviewers
|
/third_party/mesa3d/ |
D | CODEOWNERS | 1 # This file contains the GitLab handle of the maintainers/reviewers for
|
/third_party/ltp/doc/ |
D | maintainer-patch-review-checklist.txt | 16 * Check also mailing lists for other reviewers / testers tags, notes and failure reports
|
/third_party/tzdata/ |
D | CONTRIBUTING | 13 reliable sources that reviewers can check.
|
/third_party/googletest/googletest/scripts/ |
D | upload.py | 1320 if options.reviewers: 1321 for reviewer in options.reviewers.split(','): 1324 form_fields.append(("reviewers", options.reviewers))
|
/third_party/mesa3d/docs/ |
D | submittingpatches.rst | 104 This provides reviewers with quick feedback if the patch has already 182 Add labels to your MR to help reviewers find it. For example: 212 reviewers know which feedback got handled and which didn't.
|
/third_party/node/doc/guides/contributing/ |
D | pull-requests.md | 313 Feel free to post a comment in the pull request to ping reviewers if you are 332 be resolved with a bit of patience. That said, reviewers should be expected to 364 reviewers are strictly counter to the [Code of Conduct][]. 527 and the names of the reviewers). The commit history of your pull request, 547 because the reviewers have hit the buttons before.
|