@tmatsuo Do we need to be disabling the tests run via GH Actions in the Kokoro build?

@tseaver

Do we need to be disabling the tests run via GH Actions in the Kokoro build?

Sorry what do you mean?

@tmatsuo If we are running lint / unit tests / coverage / mypy via GH Actions, should we skip running them on Kokoro, restricting it to only those jobs which need secrets?

@tseaver Yes, it makes sense. Tell us which Kokoro job we should disable.
@parthea FYI

@tmatsuo

Yes, it makes sense. Tell us which Kokoro job we should disable.

For this repo, the main Kokoro build is completely covered by the GH Actions: there are no systests or samples being run. We would also need to work out the spellings to make those actions required in .kokoro/sync-repo-settings.yaml.

@parthea I added a sync_repo_settings.py here, and configured it to make the GH Actions required. However, that change isn't made during the PR review process: it gets applied by the repo automation bot only after the PR merges. Dropping the Kokoro job (but not Kokoro docs-presubmit) would need to happen in the internal google3 repo, I think -- while we're at it, we could drop the Samples jobs, too -- this repo has none.