-
Notifications
You must be signed in to change notification settings - Fork 107
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
Add support for bypass_pull_request_allowances argument from github_branch_protection resource #157
Comments
|
@shinenelson is this an issue for a new release? |
I would assume so because this is a feature that was merged into the provider fairly recently which means supporting the feature in this module would have to drop support for a lot of versions ( from 4.20 to 5.20 ). After going through most of the feature / pull requests here that might introduce breaking changes, the highest version ( that I observed ) to bump would be to 5.8.0 which is still much older than 5.20.0. My opinion is that downstream projects should support as many older versions as possible so that it includes as many users as possible. However, there are some projects that consider the opposite. I am not sure how the project maintainers consider releasing breaking changes for this project since I am not part of that group. PS : My previous comment was merely an attempt to make triaging issues easier for the project maintainers. |
@shinenelson thanks for your input, I got your point, on the other side people can just stick with an older module version if they don't want to upgrade. But i got your point. |
lesson learned -> don't use modules or unmaintained stuff with terraform |
hello folks, we will update this module once the 6.0 provide has been released https://github.com/integrations/terraform-provider-github/releases/tag/v6.0.0-rc1 |
Would be great to have this implemented as manual changes get overwritten and our automation pipelines are failing.
The text was updated successfully, but these errors were encountered: