Current github_repository documentation doesn't mention the fact that you may get an inconsistent Terraform plan also for the properties related to allow_merge_commit and allow_squash_merge. When a GitHub App fails to retrieve the state of the repository's settings through the GET method, it will always try to apply new changes ignoring the current values.
Pull request checklist
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)
Current
github_repositorydocumentation doesn't mention the fact that you may get an inconsistent Terraform plan also for the properties related toallow_merge_commitandallow_squash_merge. When a GitHub App fails to retrieve the state of the repository's settings through the GET method, it will always try to apply new changes ignoring the current values.Pull request checklist
Does this introduce a breaking change?
Please see our docs on breaking changes to help!