[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-04-04 UTC。"],[],[],null,["# Review a change\n\nThis document provides instructions on how to review a change. Keep in mind the\nfollowing criteria for a valid change:\n\n- Does this change fit within this project's stated purpose?\n- Is this change valid within the project's existing architecture?\n- Does this change introduce design flaws that could cause problems in the future?\n- Does this change follow the best practices that have been established for this project?\n- Is this change a good way to perform the described function?\n- Does this change introduce any security or instability risks, or break any existing apps?\n\nFor additional information on reviewing a change, see the\n[Reviewing a change](https://gerrit-review.googlesource.com/Documentation/intro-gerrit-walkthrough.html#_reviewing_the_change)\nsection of the Gerrit documentation.\n\nIf you are assigned to be an reviewer for a change, you should receive an email\nwith a link to the change. Follow these steps to review and review the change:\n\n1. Click the email's link to the change. Gerrit's Change Info\n screen is displayed. This screen provides a description of the change,\n identifies the contributor of the change and all reviewers, and provides a list\n of the files associated with the change.\n\n2. Read the change description to understand the objective of the change.\n\n3. Click a file to review the changes in the file. The file opens in a two pane\n comparison screen with the existing file on the left and the file with proposed\n changes on the right. To review the file:\n\n 1. Use your mouse to highlight (click + drag) the portion of code for which\n you have a comment or question. The message \"Press c to comment\" appears.\n\n 2. Press **c**. A draft comment box appears.\n\n 3. Enter your comment or question and click **SAVE**.\n\n4. Click the change's unique number (upper left side of the screen) to return\n to the Change Info screen.\n\n5. Continue reviewing each file in the change.\n\n6. When you are done reviewing all of the files in the change, return\n to the Change Info screen and click **REPLY**. The Submit requirement votes\n screen appears.\n\n7. Chose one of the following scores for the change:\n\n - +1 Looks good to me, but someone else must also approve.\n\n | **Note:** Only Google employees can give a +2 and two Google employees must give a +2 to submit a change.\n - 0 No score\n\n - -1 I would prefer this is not submitted as is, there are things to fix.\n\n - -2 This change shouldn't be submitted\n\n8. Click **REPLY** to send your comments and score to developer of the change.\n\nIf there are issues to fix, the developer fixes them and asks for you to\nreview the fixes. Otherwise, you are done reviewing the change."]]