-
Notifications
You must be signed in to change notification settings - Fork 85
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
Duplicate approvals #213
Comments
I believe the default behaviour is to re-approve when new commits are pushed to the branch ( auto-approve-action/src/approve.ts Lines 39 to 45 in aa8a692
I assume that's so that re-reviews occur when they are required by branch protections: However, the I'll try removing the check in a PR. |
Released in v3.2.0 |
I do not believe this works correctly now. I have Previously it worked correctly (albeit yes, it was duplicating sometimes, but I did not mind that). |
Thanks @pfuhrmann. It looks like it's possible to have old |
@pfuhrmann if you could confirm that you're seeing the same thing (old You can see all the reviews by running |
Hi @hmarr, thanks for coming back to me so quickly! This is what I see on the PR (redacted): [
{
"id": 1340392942,
"node_id": "PRR_kwDOH65R-s5P5MXu",
"user": {
"login": "github-actions[bot]",
},
"body": "Auto approved (low risk update)! :+1: :rocket:",
"state": "APPROVED",
"submitted_at": "2023-03-14T22:41:54Z",
"commit_id": "2e0af399a670ff3971253f69539274b1dedf13a1"
},
{
"id": 1340392945,
"node_id": "PRR_kwDOH65R-s5P5MXx",
"user": {
"login": "github-actions[bot]",
},
"body": "Auto approved (low risk update)! :+1: :rocket:",
"state": "DISMISSED",
"submitted_at": "2023-03-14T22:41:55Z",
"commit_id": "2e0af399a670ff3971253f69539274b1dedf13a1"
}
]
The full output from action is: Fetching user, pull request information, and existing reviews
Current user is github-actions[bot]
Commit SHA is 2968fc1548df680b12c727068ad3f9075c56294f
Current user already approved pull request #77, nothing to do I assume this is the state you wrote about previously, i.e. old |
Great, yeah that does look like the case I described. I've merged the PR and released v3.2.1 — hopefully that fixes the issue for you! |
@hmarr I can confirm, all our automated PRs got merged so this seems resolved. Thanks! |
After making a change to an approved path, every subsequent commit triggers a new approval. The logs say it is looking for existing reviews, but seems to not find the last one.
Logs from the second run:
workflow config:
Perhaps there's a missing permission that is preventing it from fetching existing reviews?
The text was updated successfully, but these errors were encountered: