Skip to content

Regenerate storagetransfer client #6617

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 storagetransfer client #6617

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 May 9, 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 9, 2025
@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-storagetransfer branch 2 times, most recently from 0e8501a to 0e4427b Compare May 10, 2025 01:00
@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-storagetransfer branch from 0e4427b to e69c7a6 Compare May 11, 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 11, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-storagetransfer branch from e69c7a6 to ed86752 Compare May 12, 2025 01:01
@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 12, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-storagetransfer branch from ed86752 to 385cd0e Compare May 13, 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 13, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-storagetransfer branch from 385cd0e to 7f1c86e Compare May 14, 2025 01:00
@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 14, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-storagetransfer branch from 7f1c86e to 759647c Compare May 15, 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 15, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-storagetransfer branch from 759647c to 09e5007 Compare May 16, 2025 01:04
@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 16, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-storagetransfer branch from 09e5007 to 1219917 Compare May 17, 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 17, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-storagetransfer branch from 1219917 to 7194e98 Compare May 18, 2025 01:02
@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 18, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-storagetransfer branch from 7194e98 to 9197dde Compare May 19, 2025 01:02
@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-storagetransfer branch from 7aed7b6 to 7f59f8c Compare May 22, 2025 01:01
@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-storagetransfer branch from 7f59f8c to a3f0d09 Compare May 23, 2025 01:02
@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-storagetransfer branch from a3f0d09 to 43d6007 Compare May 24, 2025 01:02
@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-storagetransfer branch from 43d6007 to 2e4c466 Compare May 25, 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 25, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-storagetransfer branch from 2e4c466 to 5e4f2e8 Compare May 26, 2025 01:02
@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-storagetransfer branch from 5e4f2e8 to 27d9bfd Compare May 27, 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 27, 2025
@yoshi-code-bot yoshi-code-bot force-pushed the regenerate-storagetransfer branch from 27d9bfd to a2f9226 Compare May 28, 2025 01:01
@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-storagetransfer branch from a2f9226 to b292bfb Compare May 29, 2025 01:02
@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-storagetransfer branch from b292bfb to efe50bc Compare May 30, 2025 01:02
@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:44
@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 d30c63c 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