Closed suztomo closed 2 months ago
Do we expect this change to be propagated to all libraries through Owlbot PRs?
Do we expect this change to be propagated to all libraries through Owlbot PRs?
Yes.
Do we expect this change to be propagated to all libraries through Owlbot PRs?
Yes.
Thanks! I don't see this file trusted-contribution.yml
in google-cloud-java, is it excluded in some steps?
I don't see this file trusted-contribution.yml in google-cloud-java, is it excluded in some steps?
There's no OwlBot configuration for google-cloud-java any more https://github.com/googleapis/google-cloud-java/tree/main/.github. Thus the postprocessor does not run.
Experiment succeeded in https://github.com/googleapis/java-bigtable/pull/2233#issuecomment-2145392263
I don't see this file trusted-contribution.yml in google-cloud-java, is it excluded in some steps?
There's no OwlBot configuration for google-cloud-java any more https://github.com/googleapis/google-cloud-java/tree/main/.github. Thus the postprocessor does not run.
We only recently removed the OwlBot configuration, but this file was introduced years ago, so this file should at least exist in google-cloud-java. Just like in java-bigtable, this file exists but a few new configs are added by this change.
The file was not there before the monorepo migraiton https://github.com/googleapis/google-cloud-java/tree/main_202208/.github.
so this file should at least exist in google-cloud-java
What observations made you think that?
The postprocessor had been running, but owlbot-java has special treatment not to process the root directory of google-cloud-java.
From reading the configuration (https://github.com/googleapis/repo-automation-bots/pull/1682/files), it accepts multiple objects.