Skip to content

Regenerate lifesciences client #6597

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 lifesciences client #6597

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-lifesciences branch from cb0a786 to 012ef44 Compare May 1, 2025 00:51
@yoshi-code-bot yoshi-code-bot requested review from yoshi-approver and a team as code owners May 1, 2025 00:51
@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 1, 2025
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label May 1, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-lifesciences branch from 012ef44 to c12be47 Compare May 2, 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 2, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-lifesciences branch from c12be47 to 93ec375 Compare May 3, 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 3, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-lifesciences branch from 93ec375 to 9843adf Compare May 4, 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 4, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-lifesciences branch from 9843adf to 862816d Compare May 5, 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 5, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-lifesciences branch from 862816d to 114b65f Compare May 6, 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 6, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-lifesciences branch from 114b65f to f14d289 Compare May 7, 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 7, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-lifesciences branch from f14d289 to db7a352 Compare May 8, 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 8, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-lifesciences branch from db7a352 to 96e1462 Compare May 9, 2025 00:52
@yoshi-approver yoshi-approver added the automerge: exact Summon MOG for automerging, but approvals need to be against the latest commit label May 9, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-lifesciences branch from 96e1462 to 53fd972 Compare May 10, 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 10, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-lifesciences branch from 53fd972 to 429e5e8 Compare May 11, 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 21, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-lifesciences branch from 2122dd5 to b32690e Compare May 22, 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 22, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-lifesciences branch from b32690e to 760af80 Compare May 23, 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 23, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-lifesciences branch from 760af80 to b7fa8f7 Compare May 24, 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 24, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-lifesciences branch from b7fa8f7 to 689ace0 Compare May 25, 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 25, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-lifesciences branch from 689ace0 to a1171d2 Compare May 26, 2025 00:52
@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-lifesciences branch from a1171d2 to 14f3a9b Compare May 27, 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 27, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-lifesciences branch from 14f3a9b to b2757e7 Compare May 28, 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 28, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-lifesciences branch from b2757e7 to 9d5a56b Compare May 29, 2025 00:52
@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-lifesciences branch from 9d5a56b to ab0adc9 Compare May 30, 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 30, 2025
@bshaffer bshaffer enabled auto-merge (squash) May 30, 2025 01:48
@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 0a6fa26 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