* but sometimes changes on release notes.md was brought to master and merged unnoticed,
 * e.g https://github.com/gradle/gradle/pull/25825
 *
 * This script is to check if there is any merge commit that brings changes from release branch to master.
 *
 * Usage (Java 11+ single-file source execution):
 *   java .teamcity/scripts/CheckBadMerge.java < commits.txt
 *
 * If any "bad" merge commit is found, it will print the details and exit with non-zero code.

If the tests are passing, you can merge it right away.

## Dependabot PRs

Dependabot will create PRs to update dependencies for several things, and those PRs all look similar, but some are way more delicate than others.

  homepage: https://maven.apache.org/ref/current
  labels:
    - java
    - build-management
    - apache-maven
    - maven
    - hacktoberfest
  enabled_merge_buttons:
    squash: true
    merge: false
    rebase: true
  autolink_jira:
    - MNG
  pull_requests:
    del_branch_on_merge: true
  protected_branches:
    master: {}
    maven-4.0.x: {}
    maven-3.10.x: {}
    maven-3.9.x: {}

- [ ] Each commit in the pull request should have a meaningful subject line and body.
  Note that commits might be squashed by a maintainer on merge.
- [ ] Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
  This may not always be possible but is a best-practice.

the ones with the label for your language. For example, for Spanish, the label is [`lang-es`](https://github.com/fastapi/fastapi/pulls?q=is%3Aopen+sort%3Aupdated-desc+label%3Alang-es+label%3Aawaiting-review).

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/...

      - name: Get coverage files
        uses: actions/download-artifact@v8
        with:
          pattern: coverage-*
          path: coverage
          merge-multiple: true
      - run: ls -la coverage
      - run: uv run coverage combine coverage
      - run: uv run coverage html --title "Coverage for ${{ github.sha }}"
      - name: Store coverage HTML

  } ]
}, {
  "scenario" : "org.gradle.performance.regression.corefeature.ExcludeRuleMergingPerformanceTest.merge exclude rules",
  "durations" : [ {
    "testProject" : "excludeRuleMergingBuild",
    "linux" : 290
  } ]
}, {
  "scenario" : "org.gradle.performance.regression.corefeature.ExcludeRuleMergingPerformanceTest.merge exclude rules (parallel)",
  "durations" : [ {
    "testProject" : "excludeRuleMergingBuild",

### Style konusunda çok dert etmeyin { #dont-worry-about-style }

* Commit message tarzı gibi şeyleri çok dert etmeyin; ben commit'leri manuel olarak düzenleyerek squash and merge yapacağım.

* Style kuralları için de endişelenmeyin; bunları kontrol eden otomatik araçlar zaten var.

Ek bir style veya tutarlılık ihtiyacı olursa, bunu doğrudan isterim ya da gerekli değişikliklerle üstüne commit eklerim.

    needs:
      - full-build
      - integration-tests
    steps:
      - name: Download Caches
        uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
        with:
          merge-multiple: true
          pattern: 'cache-${{ runner.os }}*'
          path: ${{ env.MIMIR_LOCAL }}
      - name: Publish cache
        uses: actions/cache/save@668228422ae6a00e4ad889ee87cd7109ec5666a7 # v5.0.4

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

### 不用太在意風格 { #dont-worry-about-style }

* 不要太擔心像是提交訊息（commit message）的風格，我會用 squash and merge 並手動調整提交內容。

* 也不用太在意程式碼風格規範，已經有自動化工具在檢查。

如果還有其他風格或一致性的需求，我會直接提出請求，或是在上面再補上需要的修改提交。

### 檢查程式碼 { #check-the-code }

* 檢查並閱讀程式碼，看看是否合理，**在本機執行**並確認它是否真的解決了問題。

* 然後**留言**說你做了這些，這樣我才知道你真的檢查過了。