Skip to content

chore(all): auto-regenerate gapics#3975

Merged
gcf-merge-on-green[bot] merged 3 commits intomasterfrom
regen_gocloud
Apr 22, 2021
Merged

chore(all): auto-regenerate gapics#3975
gcf-merge-on-green[bot] merged 3 commits intomasterfrom
regen_gocloud

Conversation

@yoshi-automation
Copy link
Copy Markdown
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#580

Changes:

docs(monitoring/dashboard): update links to absolute path
PiperOrigin-RevId: 369540262
Source-Link: googleapis/googleapis@3ac97c8

@google-cla google-cla Bot added the cla: yes This human has signed the Contributor License Agreement. label Apr 21, 2021
yoshi-automation added a commit to googleapis/go-genproto that referenced this pull request Apr 21, 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#3975

Changes:

docs(monitoring/dashboard): update links to absolute path
  PiperOrigin-RevId: 369540262
  Source-Link: googleapis/googleapis@3ac97c8
codyoss pushed a commit to googleapis/go-genproto that referenced this pull request Apr 21, 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#3975

Changes:

docs(monitoring/dashboard): update links to absolute path
  PiperOrigin-RevId: 369540262
  Source-Link: googleapis/googleapis@3ac97c8
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#580

Changes:

docs(monitoring/dashboard): update links to absolute path
  PiperOrigin-RevId: 369540262
  Source-Link: googleapis/googleapis@3ac97c8
@yoshi-automation yoshi-automation marked this pull request as ready for review April 21, 2021 17:04
@yoshi-automation yoshi-automation requested review from a team April 21, 2021 17:04
@yoshi-automation yoshi-automation requested a review from a team April 21, 2021 17:04
@codyoss codyoss added the automerge Merge the pull request once unit tests and other checks pass. label Apr 21, 2021
@google-cla
Copy link
Copy Markdown

google-cla Bot commented Apr 21, 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 Apr 21, 2021
@gcf-merge-on-green
Copy link
Copy Markdown
Contributor

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

@gcf-merge-on-green gcf-merge-on-green Bot removed the automerge Merge the pull request once unit tests and other checks pass. label Apr 22, 2021
@google-cla
Copy link
Copy Markdown

google-cla Bot commented Apr 22, 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.

@codyoss codyoss added cla: yes This human has signed the Contributor License Agreement. 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 Apr 22, 2021
@gcf-merge-on-green gcf-merge-on-green Bot merged commit 54e662f into master Apr 22, 2021
@gcf-merge-on-green gcf-merge-on-green Bot deleted the regen_gocloud branch April 22, 2021 15:06
@gcf-merge-on-green gcf-merge-on-green Bot removed the automerge Merge the pull request once unit tests and other checks pass. label Apr 22, 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