## Pull Request'leri İnceleyin { #review-pull-requests }

Başkalarının gönderdiği pull request'leri incelememde bana yardımcı olabilirsiniz.

Yine, lütfen elinizden geldiğince nazik olmaya çalışın. 🤗

---

Bir pull request'i incelerken akılda tutmanız gerekenler:

### Problemi anlayın { #understand-the-problem }

[well-formed commit message]: https://google.github.io/eng-practices/review/developer/cl-descriptions.html

#### Merging pull requests ####

Due to Guava's nature as a subset of Google's internal codebase which is
automatically synced to the public GitHub repository, we are unable to merge
pull requests directly into the master branch. Instead, once a pull request is
ready for merging, we'll make the appropriate changes in the internal codebase

            Please report it to @gradle/bt-support team
          close-issue-reason: not_planned

          # PULL REQUESTS -----------------------------------------------------
          days-before-pr-stale: 30
          exempt-pr-labels: "from:contributor"
          stale-pr-label: stale
          stale-pr-message: >
            This pull request has been automatically marked as stale because it has not had recent activity.

        days-before-close: 180
        stale-issue-label: "status:stale"
        exempt-issue-labels: 'type:feature,type:with reproduction steps,type:has pull request'
        stale-pr-label: 'status:stale'

          ./gradlew performance:writePerformanceTimes -Porg.gradle.performance.db.url=${{ env.PERFORMANCE_DB_URL }} -Porg.gradle.performance.db.username=${{ env.PERFORMANCE_DB_USERNAME }}
      - name: Create Pull Request
        uses: peter-evans/create-pull-request@v8
        with:
          commit-message: Update performance test durations
          branch: bot-update-performance-test-durations
          branch-suffix: timestamp

These are the people that:

* [Help others with questions in GitHub](help-fastapi.md#help-others-with-questions-in-github).
* [Create Pull Requests](help-fastapi.md#create-a-pull-request).
* Review Pull Requests, [especially important for translations](contributing.md#translations).
* Help [manage the repository](management-tasks.md) (team members).

All these tasks help maintain the repository.

**Hinweis**: Wenn Sie das tun, bitte ich Sie, auch anderen zu helfen. 😉

## Pull Requests prüfen { #review-pull-requests }

Sie können mir helfen, Pull Requests von anderen zu überprüfen.

Noch einmal, bitte versuchen Sie Ihr Bestes, freundlich zu sein. 🤗

---

Hier ist, was Sie beachten sollten und wie Sie einen Pull Request überprüfen:

### Das Problem verstehen { #understand-the-problem }

    permissions:
      contents: read
      pull-requests: write
    runs-on: ubuntu-latest
    steps:
    - uses: actions/labeler@v6
      if: ${{ github.event.action != 'labeled' && github.event.action != 'unlabeled' }}
    - run: echo "Done adding labels"
  # Run this after labeler applied labels
  check-labels:
    needs:
      - labeler
    permissions:
      pull-requests: read
    runs-on: ubuntu-latest
    steps:

* 建議一個新的**功能**。

**注意**：如果你這麼做，那我也會請你去幫助其他人。😉

## 審核 Pull Request { #review-pull-requests }

你可以幫我審查他人的 Pull Request。

再強調一次，請盡量保持友善。🤗

---

以下是審查 Pull Request 時需要注意與如何進行：

### 先理解要解的問題 { #understand-the-problem }

* 首先，確認你**理解了該 Pull Request 想解決的問題**。可能在 GitHub Discussion 或 issue 中有更長的討論。

* 也很有可能這個 Pull Request 其實不需要，因為問題可以用**不同的方法**解決。那你就可以提出或詢問那個方向。

## Revise Pull Requests { #review-pull-requests }

Você pode me ajudar revisando pull requests de outras pessoas.

Novamente, por favor tente ao máximo ser gentil. 🤗

---

Veja o que ter em mente e como revisar um pull request:

### Entenda o problema { #understand-the-problem }