git-xargs VS terraform-provider-github

No problem, I had the same question just the other day. There is also git-xargs https://github.com/gruntwork-io/git-xargs

As mentioned earlier, try https://github.com/gruntwork-io/git-xargs, no need to reinvent the wheel!

I've looked for a solution to bitbucket and github but found something only for github that I'm yet to test (https://github.com/gruntwork-io/git-xargs). Other solution I thought about, that could work with bitbucket and github, is holding a script in a bucket or something and tell each repository's pipeline configuration to download and run it at some point.

You could try https://github.com/gruntwork-io/git-xargs

One problem with multi-repo is when you have to do service across a whole infrastructure (or large segments). Like patching. It's very very helpful to have a tool like https://github.com/gruntwork-io/git-xargs to help automate these things, where possible. You still end up with a crapload of PR's. So then it's helpful to have a streamlined review process for when you need to batch review PRs for a large change like this.

There's an open feature request issue for it in the provider. I'd keep your eyes on 1534 for it to be implemented, as well as give it the 'ol thumbs-up bump.

I wanted to configure GitHub Pages using terraform because this project already uses it to configure this repository. But currently, due to how GitHub provider for terraform is written, configuring Pages requires some fiddling and will not work on the first run. During my research into how I could achieve declarative configuration for Pages, I found out that GitHub recently added actions that allow deploying to Pages without additional branch. I like this new approach better and in the future I will switch to it, but for now I decided to configure Pages manually as suggested by GitHub Pages Action that we are using.

Someone hit the wrong switch at the factory: https://github.com/integrations/terraform-provider-github/releases/tag/v4.28.0

Well, there are a lot of open issues [0] with no outlook to get them ever closed.

We've had issues with branch protection rules (the same code works with old actors in the state, but new actors erroring out without any reason), organization secrets, etc.

[0]: https://github.com/integrations/terraform-provider-github/is...

https://github.com/integrations/terraform-provider-github/is...

I don't understand how this hasn't gotten more attention throughout the years. I would like to learn about why that is.

I am a big fan of Squash and Merge but it's saddening that users have to configure that by hand on a repo when they first merge a commit via the GitHub UI, as many people aren't aware or don't think about it which can lead to nasty commit histories.

Am I missing something? Am I git'ing wrong?