Timo Sand

My current suggestion is to "swallow" the 0 value inside the provider and just keep acting like it's `1`. See: https://github.com/integrations/terraform-provider-github/pull/2976/commits/9d22505853a851df0bb542e4b5e616602a3a6304

> [@deiga](https://github.com/deiga) we'd need to make this support both `0` & `1` as I'd expect most people to have switched over to using `0` (we have). @stevehipwell That's a good...

Hey @audunsolemdal Thanks for raising this issue, I did a quick search on the GH API and the SDK and it seems that there isn't a way to skip invitations....

> I updated this morning to 6.7.5 and my initial issues are still happening unfortunately. > > The TF plan showed the following: > ``` > Terraform will perform the...

From a security standpoint, this sounds like a horrible idea to add 😬 But, it's not up to us to regulate how _you_ might use this. We're currently quite busy...

> yarn also added this now Adding references as I couldn't find a curated Yarn changelog 😬 https://medium.com/@roman_fedyskyi/yarn-4-10-adds-a-release-age-gate-for-safer-dependency-management-765c2d18149a https://yarnpkg.com/configuration/yarnrc#npmMinimalAgeGate

This sounds like the description would need to be set to ForceNew, if this is still happening

This should be resolved by https://github.com/integrations/terraform-provider-github/pull/2397