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

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

## 審核 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 }

* 提出一个**问题**或关于某个**问题**的求助。
* 建议一个新的**功能**。

**注意**：如果你这么做了，我也会请你去帮助其他人。😉

## 审阅 Pull Request { #review-pull-requests }

你可以帮我审阅他人的 Pull Request。

再次提醒，请尽力保持友善。🤗

---

下面是需要注意的点，以及如何审阅一个 Pull Request：

### 理解问题 { #understand-the-problem }

* 首先，确保你**理解这个 PR 要解决的问题**。它可能在 GitHub Discussion 或 issue 中有更长的讨论。

jobs:
  main:
    permissions:
      contents: read
      pull-requests: write
    runs-on: ubuntu-latest
    steps:
      - name: Check if PRs have merge conflicts
        uses: eps1lon/actions-label-merge-conflict@v3
        with:
          dirtyLabel: "conflicts"
          repoToken: "${{ secrets.GITHUB_TOKEN }}"

              <exclude>org.apache.maven.model.io.xpp3.MavenXpp3Reader#read(org.codehaus.plexus.util.xml.pull.XmlPullParser,boolean):METHOD_REMOVED</exclude>
              <exclude>org.apache.maven.model.io.xpp3.MavenXpp3ReaderEx#contentTransformer</exclude>
              <exclude>org.apache.maven.model.io.xpp3.MavenXpp3ReaderEx#read(org.codehaus.plexus.util.xml.pull.XmlPullParser,boolean):METHOD_REMOVED</exclude>

**Nota**: si lo haces, entonces te voy a pedir que también ayudes a otros. 😉

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

Puedes ayudarme a revisar pull requests de otros.

De nuevo, por favor, haz tu mejor esfuerzo por ser amable. 🤗

---

Aquí está lo que debes tener en cuenta y cómo revisar un pull request:

### Entiende el problema { #understand-the-problem }

# MinIO Pull Request Guidelines

These guidelines ensure high-quality commits in MinIO’s GitHub repositories, maintaining 
a clear, valuable commit history for our open-source projects. They apply to all contributors, 
fostering efficient reviews and robust code.

## Why Pull Requests?

Pull Requests (PRs) drive quality in MinIO’s codebase by:
- Enabling peer review without pair programming.
- Documenting changes for future reference.

### GNU/Linux and macOS

```sh
docker-compose pull
docker-compose up
```

or

```sh
docker stack deploy --compose-file docker-compose.yaml minio
```

### Windows

```sh
docker-compose.exe pull
docker-compose.exe up
```

or

```sh
docker stack deploy --compose-file docker-compose.yaml minio
```

## Pull Request 리뷰하기 { #review-pull-requests }

다른 사람들이 만든 pull request를 리뷰하는 데 저를 도와줄 수 있습니다.

다시 한번 말하지만, 최대한 친절하게 리뷰해 주세요. 🤗

---

Pull request를 리뷰할 때 고려해야 할 사항과 방법은 다음과 같습니다:

### 문제 이해하기 { #understand-the-problem }

* 먼저, 해당 pull request가 해결하려는 **문제를 이해하는지** 확인하세요. GitHub Discussion 또는 이슈에서 더 긴 논의가 있었을 수도 있습니다.

#!/bin/bash
set -e

# Script to update Gradle wrapper and create a pull request
# 
# Usage:
#   ./update_wrapper_and_create_pr.sh [wrapper_version]
#
# Arguments:
#   wrapper_version - The Gradle version to update the wrapper to
# 
# Environment variables:
#   DEFAULT_BRANCH  - The default branch to create the pull request on (e.g. "master"/"release")
#   GITHUB_TOKEN    - GitHub bot token