Where are the maintainers?

[fatbasstard]

Hi,

286 issues open, 87 PR's open. Lasted merged PR from April 8. No response on issues and PR's.

What's going on, where's the support?

[odeatavanade]

@nickfloyd / @kfcampbell I see you are the one to approve the latest merged PRs ...

Any update on the future of this provider?

[kishaningithub]

Looks like they are busy with other work and are trying to allocate atleast 1 day per month to support this integration

Ref: https://github.com/integrations/terraform-provider-github/pull/2615#issue-2980411384

[Satak]

Oh no. Could there ne possibility to point some individuals from community to be part of the core team so we could get better support for this provider?

[jackivanov]

This project was born and shaped inside GitHub, and realistically, it's hard to see some one like HashiCorp stepping in to take ownership at this point. Without clear direction, it risks slowly fading into irrelevance (and arguably, it already has).

But that doesn't have to be the end of the story, we should start thinking seriously about a community-driven fork. That means more than just duplicating the code. It would require forming an open source committee, putting basic governance in place, and rallying maintainers who believe in its future.

[sfuerte]

Given the provider's download stats and the whole IaC / GitOps ideology, it's rather weird GitHub (as the Org) isn't that interested in supporting this TF provider.

it's hard to see some one like HashiCorp stepping in to take ownership at this point

there is OpenTofu Registry also available.

[sfuerte]

as an option, as well as for promoting discussion and upvoting there 😃 https://github.com/orgs/opentofu/discussions/3019

[odeatavanade]

hi. I have been using it for 2 months now ... and to be honest, I am seriously thinking about abandoning the idea to use this provider to maintain my GitHub Infrastructures.

• Using one enterprise level admin login, it is a challenge to administer organizations as it is a provider configuration (forget about the for_each to configure orgs in depth)
• EMU features are limited. The best example is the Team management ... impossible to link a team to an Entra ID group (or I am totally stupid)
• Lack of Enterprise level resources / data
• ...

I have even been looking at how to implement a terraform provider with C# (Go doesn't like me) and implement something from the ground (spoiler: it might work but it takes a looooooooot of time to implement everything). I will try to share some code when I get the time to

[fatbasstard]

We're getting to the point to fork this repository.

How can a widely and actively used ("Hashicorp") provider that helps with maintaining vital parts of infrastructure be abandoned in this way.

Shame on GitHub for pulling development capacity away

[grimm26]

sure is a lot of development going on at gitlab https://gitlab.com/gitlab-org/terraform-provider-gitlab

[tnm]

I've officially written off this repo, and have forked it off to https://github.com/cased/terraform-provider-github

help wanted! https://github.com/cased/terraform-provider-github/blob/main/README.md

[mkushakov]

We have forked this terraform provider as we heavily relaying on it. Also we take opportunity to rewrite it with modern terraform framework instead of old plugin SDK. On top of it we fix some issues with ruleset and update go-github sdk which was alsmot 1 years old to more recent v74. Please feel free to use it and we will start adding more features. We are not ready to accept contributions in this projects, but feel free to open issues and we will try to triage it. https://github.com/nexthink-oss/terraform-provider-github

https://registry.terraform.io/providers/nexthink-oss/github/latest

[doughlass]

All I want is full ruleset capability but the GitHub provider doesn't cater for it 😔

[eyalgal]

Thank you for raising these concerns and for your patience.

I want to acknowledge the frustration caused by the recent gaps in maintenance. We have just released version v6.7.0 of the provider, which is a major release and one of only a few planned soon as we focus on stabilizing the project and improving the overall experience for the community.

Over the next month, our main goals are to stabilize the repository, identify and onboard new maintainers from both the community and GitHub, and lay the groundwork for ongoing, consistent maintenance. We are committed to making meaningful progress and restoring trust in the project’s future.

For more details about our stabilization plans and our call for co-maintainers, please see this discussion post.

Thank you again for your feedback, advocacy, and involvement. They are critical to the future of this project.