Hi @Knight-ZXW. Thanks for your PR.

I'm waiting for a firebase member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

/ok-to-test

@jeremyjiang-dev could you merge this MR?

/test api-information-check

/retest

@yifanyang Could you take a look why the api check is still in progress?

@jeremyjiang-dev

@yifanyang Could you take a look why the api check is still in progress?

We recently migrated presubmit jobs to GitHub Actions. I suppose this pull request was created during the short period where the the api job was removed from Prow, but GitHub is still expecting it. Anyway, I have merged it manually.

@jeremyjiang-dev

@yifanyang Could you take a look why the api check is still in progress?

We recently migrated presubmit jobs to GitHub Actions. I suppose this pull request was created during the short period where the the api job was removed from Prow, but GitHub is still expecting it. Anyway, I have merged it manually.

Thank you, Yifan!