Skip to content

Regenerate analyticshub client #6515

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
May 30, 2025
Merged

Regenerate analyticshub client #6515

merged 2 commits into from
May 30, 2025

Conversation

yoshi-code-bot
Copy link
Contributor

@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from fb1d3d2 to 779a500 Compare April 16, 2025 00:50
@yoshi-code-bot yoshi-code-bot requested review from yoshi-approver and a team as code owners April 16, 2025 00:50
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Apr 16, 2025
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label Apr 16, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from 779a500 to 19ba564 Compare April 17, 2025 00:50
@gcf-merge-on-green GCF Merge on Green
Copy link

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: exact Summon MOG for automerging, but approvals need to be against the latest commit label Apr 17, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from 19ba564 to b36939e Compare April 18, 2025 00:50
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label Apr 18, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from b36939e to b09c47d Compare April 19, 2025 00:50
@gcf-merge-on-green GCF Merge on Green
Copy link

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: exact Summon MOG for automerging, but approvals need to be against the latest commit label Apr 19, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from b09c47d to 03d7101 Compare April 20, 2025 00:50
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label Apr 20, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from 03d7101 to 8449ec5 Compare April 21, 2025 00:51
@gcf-merge-on-green GCF Merge on Green
Copy link

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: exact Summon MOG for automerging, but approvals need to be against the latest commit label Apr 21, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from 8449ec5 to d8b9729 Compare April 22, 2025 00:50
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label Apr 22, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from d8b9729 to 3a68179 Compare April 23, 2025 00:50
@gcf-merge-on-green GCF Merge on Green
Copy link

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: exact Summon MOG for automerging, but approvals need to be against the latest commit label Apr 23, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from 3a68179 to ee8ef9e Compare April 24, 2025 00:50
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label Apr 24, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from ee8ef9e to 4f84e4d Compare April 25, 2025 00:50
@gcf-merge-on-green GCF Merge on Green
Copy link

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: exact Summon MOG for automerging, but approvals need to be against the latest commit label Apr 25, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from 4f84e4d to 9f13d56 Compare April 26, 2025 00:50
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from a656ab7 to 2670afc Compare May 21, 2025 00:51
@gcf-merge-on-green GCF Merge on Green
Copy link

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: exact Summon MOG for automerging, but approvals need to be against the latest commit label May 21, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from 2670afc to 9a01b1e Compare May 22, 2025 00:50
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label May 22, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from 9a01b1e to e50b028 Compare May 23, 2025 00:51
@gcf-merge-on-green GCF Merge on Green
Copy link

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: exact Summon MOG for automerging, but approvals need to be against the latest commit label May 23, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from e50b028 to f9b35a3 Compare May 24, 2025 00:50
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label May 24, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from f9b35a3 to 7c061e0 Compare May 25, 2025 00:51
@gcf-merge-on-green GCF Merge on Green
Copy link

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: exact Summon MOG for automerging, but approvals need to be against the latest commit label May 25, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from 7c061e0 to ec9602a Compare May 26, 2025 00:51
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label May 26, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from ec9602a to 64789b6 Compare May 27, 2025 00:50
@gcf-merge-on-green GCF Merge on Green
Copy link

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: exact Summon MOG for automerging, but approvals need to be against the latest commit label May 27, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from 64789b6 to 9c38382 Compare May 28, 2025 00:51
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label May 28, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from 9c38382 to c1b54c1 Compare May 29, 2025 00:51
@gcf-merge-on-green GCF Merge on Green
Copy link

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: exact Summon MOG for automerging, but approvals need to be against the latest commit label May 29, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-analyticshub branch from c1b54c1 to 9095bde Compare May 30, 2025 00:51
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label May 30, 2025
@bshaffer bshaffer enabled auto-merge (squash) May 30, 2025 01:16
@bshaffer bshaffer merged commit abdacc0 into googleapis:main May 30, 2025
10 of 11 checks passed
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label May 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@yoshi-approver yoshi-approver yoshi-approver approved these changes

Assignees
No one assigned
Labels
kokoro:force-run Add this label to force Kokoro to re-run the tests.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@yoshi-code-bot @yoshi-approver @bshaffer