-
Notifications
You must be signed in to change notification settings - Fork 763
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
Branch protection not updating #617
Comments
It appears #614 will not fix this issue. I can confirm the above behavior where it's not just a diff suppression issue, but actually not applying the expected status check. According to the docs, it should be turning on the setting requiring the branch be up to date.
|
Today I found that in order for those contexts to be applied, the groups that you're attempting to add must be in the repository permission list. Once I added the resource block below, the group was able to actually be applied to the context list in GH.
This is also true in the UI because if that group isn't listed in the repo collaboration list, then they don't show up in the search. Regardless, it would be helpful if TF didn't appear to continually re-add those groups, or say that the addition was successful, but could somehow provide some type of error as to what happened. |
@tbalasavage thank you you saved my day |
👋 Hey Friends, this issue has been automatically marked as |
Terraform Version
Terraform v0.13.5
provider registry.terraform.io/hashicorp/github v4.1.0
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Expected Behavior
The branch protection for
develop
should have been updated to have push restrictions to the teams identified as well as have status checks set.Actual Behavior
No push restrictions were added and no status checks are required but they were identified to at least have been attempted and were marked as successfully updated.
Steps to Reproduce
terraform apply
Important Factoids
Nothing in particular
The text was updated successfully, but these errors were encountered: