*       even on an {@code ImmutableMap<K, @NonNull String>}.
 * </ul>
 *
 * <p>Consumers of this annotation include:
 *
 * <ul>
 *   <li>NullAway, which <a
 *       href="https://github.com/google/guava/issues/6126#issuecomment-1204399671">treats it
 *       identically to {@code Nullable}</a> as of version 0.9.9.
 *   <li><a href="https://developers.google.com/j2objc">J2ObjC</a>, maybe: It might no longer be

    - cron: '0 0 * * *'
  workflow_dispatch:

permissions:
  issues: write

concurrency:
  group: lock

jobs:
  action:
    runs-on: ubuntu-latest
    steps:
      - uses: dessant/lock-threads@v3
        with:
          github-token: ${{ github.token }}
          issue-inactive-days: '365'
          exclude-any-issue-labels: 'do-not-close'
          issue-lock-reason: 'resolved'

# Uses the [hub](https://hub.github.com/) CLI command to issue API requests to GitHub.
# This script must be executed from the branch associated with the PR to issue the command on.
#

PR_NUMBER=$(hub pr show -f '%I')

Guava, the best approach is to create an [issue][] (or comment on an existing
issue if there is one) requesting the feature and describing specific use cases
for it.

If we decide to pursue a feature request, it will go through a thorough process
of API design and review. Any code should come after this.

[APIs]: https://en.wikipedia.org/wiki/API
[issue]: https://github.com/google/guava/issues

Pull requests
-------------

#  See the License for the specific language governing permissions and
#  limitations under the License.
#

# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser

blank_issues_enabled: false

contact_links:

  - name: Project Mailing Lists
    url: https://maven.apache.org/mailing-lists.html

permissions: {}

jobs:
  check_pull_metadata:
    permissions:
      issues: write
      pull-requests: write
    runs-on: ubuntu-latest
    steps:
      # Check that PRs have proper metadata: labels and milestone
      # https://github.com/gradle/issue-management-action/blob/main/src/pull-metadata.ts

Empty directory for test, see https://golang.org/issues/29837....

                    context.success("Maven 4 compatibility issues fixed");
                    modifiedPoms.add(pomPath);
                } else {
                    context.success("No Maven 4 compatibility issues found");
                }
            } catch (Exception e) {
                context.failure("Failed to fix Maven 4 compatibility issues" + ": " + e.getMessage());
                errorPoms.add(pomPath);

* 现在，如果问题已解决，你可以请他们：
    * 在 GitHub Discussions 中：将你的评论标记为**答案**。
    * 在 GitHub Issues 中：**关闭**该 issue。

## 关注 GitHub 资源库 { #watch-the-github-repository }

你可以在 GitHub 上「关注」FastAPI（点击右上角的「watch」按钮）：[https://github.com/fastapi/fastapi](https://github.com/fastapi/fastapi)。👀

如果你选择「Watching」而非「Releases only」，当有人创建新的 issue 或问题时你会收到通知。你也可以指定只通知新 issues、discussions、PR 等。

然后你就可以尝试帮助他们解决这些问题。

## 提问 { #ask-questions }

If the behavior is threatening or harassing, or for other reasons requires immediate escalation, please see below.