Skip to content

Regenerate cloudtrace client #6549

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 cloudtrace client #6549

merged 2 commits into from
May 30, 2025

Conversation

yoshi-code-bot
Copy link
Contributor

@yoshi-code-bot yoshi-code-bot requested review from yoshi-approver and a team as code owners April 19, 2025 00:56
@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 19, 2025
@yoshi-approver yoshi-approver added 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-cloudtrace branch from be37417 to e8aa078 Compare April 20, 2025 00:57
@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 20, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-cloudtrace branch from e8aa078 to c758fdf Compare April 21, 2025 00:57
@yoshi-approver yoshi-approver added 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-cloudtrace branch from c758fdf to b1f0b35 Compare April 22, 2025 00:57
@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 22, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-cloudtrace branch from b1f0b35 to 2a8dda3 Compare April 23, 2025 00:57
@yoshi-approver yoshi-approver added 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-cloudtrace branch from 2a8dda3 to e546c0e Compare April 24, 2025 00:57
@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 24, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-cloudtrace branch from e546c0e to 4e19511 Compare April 25, 2025 00:57
@yoshi-approver yoshi-approver added 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-cloudtrace branch from 4e19511 to 84c6ef9 Compare April 26, 2025 00:57
@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 26, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-cloudtrace branch from 84c6ef9 to 3963250 Compare April 27, 2025 00:57
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label Apr 27, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-cloudtrace branch from 3963250 to df831fd Compare April 28, 2025 00:57
@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 28, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-cloudtrace branch from df831fd to 733f648 Compare April 29, 2025 00:56
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label Apr 29, 2025
@yoshi-approver yoshi-approver added 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-cloudtrace branch from b7b09fd to 196613e Compare May 22, 2025 00:58
@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 22, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-cloudtrace branch from 196613e to 19018f1 Compare May 23, 2025 00:58
@yoshi-approver yoshi-approver added 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-cloudtrace branch from 19018f1 to 8a50deb Compare May 24, 2025 00:58
@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 24, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-cloudtrace branch from 8a50deb to c4af276 Compare May 25, 2025 00:58
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label May 25, 2025
@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 26, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-cloudtrace branch from c4af276 to cb5517d Compare May 26, 2025 00:58
@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-cloudtrace branch from cb5517d to 1d14e21 Compare May 27, 2025 00:58
@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-cloudtrace branch from 1d14e21 to eefc044 Compare May 28, 2025 00:58
@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-cloudtrace branch from eefc044 to 3095177 Compare May 29, 2025 00:57
@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-cloudtrace branch from 3095177 to 06dd6d9 Compare May 30, 2025 00:58
@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:35
@bshaffer bshaffer merged commit a0aa11a 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