fix: revert branch protection feature causing breaking change #3321
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
what
Currently as it stands in the latest release and since 0.23.2, repositories with branch protections enabled are seeing a breaking change to their workflows.
why
In summary, the GH user used by Atlantis to interface with GitHub API is unable to access the branch protection endpoint unless their permissions are set to
Admin
. Currently, we only advertiseWrite
access` for the user. See docsNote: GH Apps are unaffected since they are should be giving
Read
permissions on repo "Administration"references
Require Linear History
when selecting merge method (fix: allowRequire Linear History
when selecting merge method #3211)"admin
repo permissions #3320