Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
Now that we set up daily hermetic build generation which would creates one PR for googleapis proto changes for all services, and it has been working consistently for the last ~4 weeks, we can safely disable OwlBot PRs.
How
OwlBot is installed org wide and we can not disable it for a single repo. The bot uses the existence of
.OwlBot.yaml
to determine if a PR needs to be created. Hence, in order to disable OwlBot PRs, all.OwlBot.yaml
files are renamed to.Owlbot-hermetic.yaml
, all references to.OwlBot.yaml
are also updated.Next
Once this PR is merged, the hermetic build generation will start to fail due to the assumption in hermetic build scripts that each library must contains a
.OwlBot.yaml
file. A follow up PR will be created insdk-platform-java
to address it.