You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On github anyone who can see the repo (even with read permission) can submit reviews to a pull request, even approve them, but that won't count into required reviews, PR cannot be merged until someone with write permission reviews the PR.
As far as I can see the current implementation will simply go through all the submitted reviews and checks if at least one of them is APPROVED.
This is a bit deceptive, because one would assume that Atlantis checks if according to Github the PR is reviewed or not.
Also, this seems to be the only access control possibility based on the documentation for now, and it doesn't work as one would assume.
For the short term clarifying this in the README would probably be nice (happy to provide a PR), for the long term it would be nice to provide some access control features (maybe check if a github PR is properly approved).
Unfortunately, after a quick look at Github's API, the only way to do that for now is checking the mergability of the PR, but that includes every other configured status checks (which might not be a bad thing, but that's not about approval anymore, so won't fit into this option).
The text was updated successfully, but these errors were encountered:
On github anyone who can see the repo (even with read permission) can submit reviews to a pull request, even approve them, but that won't count into required reviews, PR cannot be merged until someone with write permission reviews the PR.
As far as I can see the current implementation will simply go through all the submitted reviews and checks if at least one of them is APPROVED.
This is a bit deceptive, because one would assume that Atlantis checks if according to Github the PR is reviewed or not.
Also, this seems to be the only access control possibility based on the documentation for now, and it doesn't work as one would assume.
For the short term clarifying this in the README would probably be nice (happy to provide a PR), for the long term it would be nice to provide some access control features (maybe check if a github PR is properly approved).
Unfortunately, after a quick look at Github's API, the only way to do that for now is checking the mergability of the PR, but that includes every other configured status checks (which might not be a bad thing, but that's not about approval anymore, so won't fit into this option).
The text was updated successfully, but these errors were encountered: