Skip to content

Regenerate serviceusage client #6636

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.

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

Merged
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-serviceusage branch from c95abb5 to 68607c5 Compare May 22, 2025 01:00
@yoshi-code-bot yoshi-code-bot requested review from yoshi-approver and a team as code owners May 22, 2025 01:00
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label May 22, 2025
@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-serviceusage branch from 68607c5 to f85840f Compare May 23, 2025 01:00
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-serviceusage branch from f85840f to 18d8cda Compare May 24, 2025 01:00
@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-serviceusage branch from 18d8cda to 7e6ce04 Compare May 25, 2025 01:00
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-serviceusage branch from 7e6ce04 to 3a0a0ee Compare May 26, 2025 01:01
@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
@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-serviceusage branch from 3a0a0ee to 0bb8add Compare May 27, 2025 01:00
@yoshi-approver yoshi-approver added 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-serviceusage branch from 0bb8add to e5ab87d Compare May 28, 2025 01:00
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 28, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-serviceusage branch from e5ab87d to cf50d7b Compare May 29, 2025 01:00
@yoshi-approver yoshi-approver added 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-serviceusage branch from cf50d7b to 744502d Compare May 30, 2025 01:01
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 30, 2025
@bshaffer bshaffer enabled auto-merge (squash) May 30, 2025 01:45
@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 merged commit 076c796 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
Labels
kokoro:force-run Add this label to force Kokoro to re-run the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants