Skip to content

Conversation

@yoshi-automation
Copy link
Contributor

This is an auto-generated regeneration of the gapic clients by
cloud.google.com/go/internal/gapicgen. Once the corresponding genproto PR is
submitted, genbot will update this PR with a newer dependency to the newer
version of genproto and assign reviewers to this PR.

If you have been assigned to review this PR, please:

  • Ensure that the version of genproto in go.mod has been updated.
  • Ensure that CI is passing. If it's failing, it requires your manual attention.
  • Approve and submit this PR if you believe it's ready to ship.

Corresponding genproto PR: googleapis/go-genproto#644

Changes:

chore(datastore/admin): Remove redundant service config YAML
The two files (datastore_v1.yaml and datastore_admin_v1.yaml) are identical, but the former is what is generated by our publication pipeline.

PiperOrigin-RevId: 386255743
Source-Link: googleapis/googleapis@b1844c9

yoshi-automation added a commit to googleapis/go-genproto that referenced this pull request Jul 23, 2021
This is an auto-generated regeneration of the .pb.go files by
cloud.google.com/go/internal/gapicgen. Once this PR is submitted, genbot will
update the corresponding PR to depend on the newer version of go-genproto, and
assign reviewers. Whilst this or any regen PR is open in go-genproto, genbot
will not create any more regeneration PRs. If all regen PRs are closed,
gapicgen will create a new set of regeneration PRs once per night.

If you have been assigned to review this PR, please:

- Ensure that CI is passing. If it's failing, it requires your manual attention.
- Approve and submit this PR if you believe it's ready to ship. That will prompt
genbot to assign reviewers to the google-cloud-go PR.

Corresponding google-cloud-go PR: googleapis/google-cloud-go#4491

Changes:

feat:Publish Workflows execution logging proto for documentation
  PiperOrigin-RevId: 386290605
  Source-Link: googleapis/googleapis@11d5ead

chore(datastore/admin): Remove redundant service config YAML
  The two files (datastore_v1.yaml and datastore_admin_v1.yaml) are identical, but the former is what is generated by our publication pipeline.

  PiperOrigin-RevId: 386255743
  Source-Link: googleapis/googleapis@b1844c9
@google-cla google-cla bot added the cla: yes This human has signed the Contributor License Agreement. label Jul 23, 2021
@snippet-bot
Copy link

snippet-bot bot commented Jul 23, 2021

Here is the summary of possible violations 😱

Details

There are 7 possible violations for not having product prefix.

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 20 region tags.

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

  • Refresh this comment

codyoss pushed a commit to googleapis/go-genproto that referenced this pull request Jul 26, 2021
This is an auto-generated regeneration of the .pb.go files by
cloud.google.com/go/internal/gapicgen. Once this PR is submitted, genbot will
update the corresponding PR to depend on the newer version of go-genproto, and
assign reviewers. Whilst this or any regen PR is open in go-genproto, genbot
will not create any more regeneration PRs. If all regen PRs are closed,
gapicgen will create a new set of regeneration PRs once per night.

If you have been assigned to review this PR, please:

- Ensure that CI is passing. If it's failing, it requires your manual attention.
- Approve and submit this PR if you believe it's ready to ship. That will prompt
genbot to assign reviewers to the google-cloud-go PR.

Corresponding google-cloud-go PR: googleapis/google-cloud-go#4491

Changes:

feat:Publish Workflows execution logging proto for documentation
  PiperOrigin-RevId: 386290605
  Source-Link: googleapis/googleapis@11d5ead

chore(datastore/admin): Remove redundant service config YAML
  The two files (datastore_v1.yaml and datastore_admin_v1.yaml) are identical, but the former is what is generated by our publication pipeline.

  PiperOrigin-RevId: 386255743
  Source-Link: googleapis/googleapis@b1844c9
This is an auto-generated regeneration of the gapic clients by
cloud.google.com/go/internal/gapicgen. Once the corresponding genproto PR is
submitted, genbot will update this PR with a newer dependency to the newer
version of genproto and assign reviewers to this PR.

If you have been assigned to review this PR, please:

- Ensure that the version of genproto in go.mod has been updated.
- Ensure that CI is passing. If it's failing, it requires your manual attention.
- Approve and submit this PR if you believe it's ready to ship.

Corresponding genproto PR: googleapis/go-genproto#644

Changes:

chore(datastore/admin): Remove redundant service config YAML
  The two files (datastore_v1.yaml and datastore_admin_v1.yaml) are identical, but the former is what is generated by our publication pipeline.

  PiperOrigin-RevId: 386255743
  Source-Link: googleapis/googleapis@b1844c9
@yoshi-automation yoshi-automation marked this pull request as ready for review July 26, 2021 15:05
@yoshi-automation yoshi-automation requested a review from a team July 26, 2021 15:05
@yoshi-automation yoshi-automation requested a review from a team as a code owner July 26, 2021 15:05
@yoshi-automation yoshi-automation requested a review from a team July 26, 2021 15:05
@yoshi-automation yoshi-automation requested a review from a team as a code owner July 26, 2021 15:05
@google-cla
Copy link

google-cla bot commented Jul 26, 2021

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Jul 26, 2021
@codyoss codyoss added automerge Merge the pull request once unit tests and other checks pass. and removed cla: no This human has *not* signed the Contributor License Agreement. labels Jul 26, 2021
@codyoss codyoss added the cla: yes This human has signed the Contributor License Agreement. label Jul 26, 2021
@google-cla
Copy link

google-cla bot commented Jul 26, 2021

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Jul 26, 2021
@codyoss codyoss added cla: yes This human has signed the Contributor License Agreement. and removed cla: no This human has *not* signed the Contributor License Agreement. labels Jul 26, 2021
@gcf-merge-on-green gcf-merge-on-green bot merged commit e5019de into master Jul 26, 2021
@gcf-merge-on-green gcf-merge-on-green bot deleted the regen_gocloud branch July 26, 2021 17:30
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Jul 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants