feat(internal/postprocessor): make OwlBot postprocessor#7202
Conversation
feat(postprocessor): integrate OwlBot locally and add basic post-processor to copy generated code into libraries
…utput directory for snippets to go into local repo internal/generated/snippets
…ient and lints that same client, skips all others
refactor(internal): Move gensnippets files to internal
…ig.go. Move cloning of google-cloud-go to main()
feat(postprocessor): rewrite OwlBot PR title and body commits to include scope
|
Here is the summary of possible violations 😱 DetailsThere is a possible violation for not having product prefix.There is a format violation for a region tag.The end of the violation section. All the stuff below is FYI purposes only. Here is the summary of changes. You are about to add 1 region tag.You are about to delete 1 region tag.This comment is generated by snippet-bot.
|
codyoss
left a comment
There was a problem hiding this comment.
Two small nits and the PR needs to be updated and resolve a merge conflict.
noahdietz
left a comment
There was a problem hiding this comment.
Cool stuff @adrianajg ! If any of my comments refer to code that was strictly moved directories, feel free to ignore them. They are all style nits anyways :)
adrianajg
left a comment
There was a problem hiding this comment.
Thanks for the review! I addressed your comments, sometimes with additional tweaks. I also updated the README.md as I noticed there was some outdated info there. Let me know if you see anything else.
|
🎉 |
OwlBot will be configured to copy generated files directly into their corresponding client directories. When triggered by the OwlBot automation robot, the postprocessor performs the following tasks:
$ go mod tidyin all repo directories$ gofmt -s -d -w -l .in all repo directories.github.OwlBot.yamlfile must include anapi-namefield with the valueREPLACEMEin order to label all commit messages with the placeholder scope '[REPLACEME]'.