-
Notifications
You must be signed in to change notification settings - Fork 228
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
feat: add service_account_email for export subscriptions #1927
Conversation
Owl bot is regenerating pull request 1927... |
PiperOrigin-RevId: 638641437 Source-Link: googleapis/googleapis@a3016a8 Source-Link: googleapis/googleapis-gen@2001c33 Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiMjAwMWMzMzBhZWU2MmE5ZDRlOGE5ODUyZDhlNWJmMjY2MjgxOGFkNCJ9
e986512
to
6b8094b
Compare
This review does not reference the most recent commit, and you are using the secure version of merge-on-green. Please re-review the most recent commit.
This review does not reference the most recent commit, and you are using the secure version of merge-on-green. Please re-review the most recent commit.
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. |
) I noticed in googleapis/nodejs-pubsub#1927 that merge-on-green kept dismissing auto-approve's latest review due to post-processor updates, other commits, etc. Ideally, those commits would retrigger auto-approve to re-review the PR. But there seems to be a race condition where sometimes merge-on-green beats auto-approve to re-approving and dismisses the PR. This fix would allow auto-approve to listen to reviews dismissed, so that it always has a chance to re-review the most recent commit when an `automerge: exact` label has been placed. As part of this work, the pull_request_review.dismissed event needs to access the pr number through [`pull_request.number`](https://docs.github.com/en/webhooks/webhook-events-and-payloads#pull_request_review), so I had to update this for all the events and make sure the test fixtures had the appropriate number there too. Fixes #5096
PiperOrigin-RevId: 638641437
Source-Link: googleapis/googleapis@a3016a8
Source-Link: https://github.com/googleapis/googleapis-gen/commit/2001c330aee62a9d4e8a9852d8e5bf2662818ad4
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiMjAwMWMzMzBhZWU2MmE5ZDRlOGE5ODUyZDhlNWJmMjY2MjgxOGFkNCJ9