* GCE provider: Create TargetPool with 200 instances, then update with rest ([#27865](https://github.com/kubernetes/kubernetes/pull/27865), [@zmerlynn](https://github.com/zmerlynn))
* GCE provider: Limit Filter calls to regexps rather than large blobs ([#27741](https://github.com/kubernetes/kubernetes/pull/27741), [@zmerlynn](https://github.com/zmerlynn))

pull requests are approved and pass continuous integration checks, a TensorFlow
team member will apply `ready to pull` label to your change. This means we are
working on getting your pull request submitted to our internal repository. After
the change has been submitted internally, your pull request will be merged
automatically on GitHub.

If you want to contribute, start working through the TensorFlow codebase,

You can also review already merged translation PRs. To do this, go to the [closed pull requests](https://github.com/fastapi/fastapi/pulls?q=is%3Apr+is%3Aclosed) and filter by your language label. For example, for Spanish, you can use [`lang-es`](https://github.com/fastapi/fastapi/pulls?q=is%3Apr+is%3Aclosed+label%3Alang-es).

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

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

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

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

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

---

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

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

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

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

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

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

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

---

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

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

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

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

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

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

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

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

---

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

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

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

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

You can help me review pull requests from others.

Again, please try your best to be kind. 🤗

---

Here's what to keep in mind and how to review a pull request:

### Understand the problem { #understand-the-problem }

4. Submit a pull request

You must agree to the terms of [Developer Certificate of Origin](https://developercertificate.org/) by signing off your commits. We automatically verify that all commit messages contain a `Signed-off-by:` line with your email address. We can only accept PRs that have all commits signed off.

If you didn't sign off your commits before creating the pull request, you can fix that after the fact.

- If the description (the text inside the title attribute) contains the full phrase for this abbreviation, then append a dash (-) to the full phrase, followed by the translation of the full phrase.

Conversion scheme:

Source (English):

```
<abbr title="{full phrase}">{abbreviation}</abbr>
```

Result:

```
<abbr title="{full phrase} - {translation of full phrase}">{abbreviation}</abbr>
```

Examples: