Upcoming stabilization work and call for co-maintainers

[eyalgal]

Starting today (10/20/2025), we’re dedicating one month to stabilizing this project, focusing on high-priority PRs and issues.

During this time, you can expect increased activity and engagement from the GitHub team.

You can track what we're working on and our progress on this board.

We are also seeking co-maintainers from the community to help with ongoing maintenance. If you're interested, please reply to this discussion.

Basic criteria for co-maintainers:

• Familiarity with Terraform and the GitHub API
• Ability to review code, manage issues, and respond to community questions
• Commitment to regular activity (suggest at least a few hours per week)
• Respectful and constructive communication with contributors and users
• Willingness to collaborate with the existing maintainers and follow project guidelines

Thanks for your support.

[TommyHyland-sudo]

I am interested and would be happy to be a co-maintainer.

Majority of my experience and code lies in other work accounts so please don't use this account as a reference for my work.

I'd be more than happy to have a discussion to see if I'm eligible or not.

[ViacheslavKudinov]

Hi @eyalgal
Maybe this one is better to rephrase

Familiarity with Terraform and the GitHub API

To something like:
Familiarity with Terraform plugin SDK, Golang and the GitHub API

[stevehipwell]

I'm interested in helping to maintain this provider.

[stevehipwell]

@nickfloyd I got an invitation but it was cancelled?

[nickfloyd]

I issued another one would you mind looking at the invites again: https://github.com/integrations/terraform-provider-github/invitations

[stevehipwell]

Thanks @nickfloyd, all sorted. I had to use a browser as it wasn't working in my Android app.

[eyalgal]

I'm excited to share that version v6.7.0 of the provider has just been released! 🎉

This is a major release and one of the few planned soon as we focus on stabilizing the project.

A huge thank you to everyone who contributed, whether through code, feedback, or testing, and to all who have reached out (both here and directly) to help maintain and improve this project. Your support and willingness to get involved are invaluable.

Let’s keep up the great momentum! 🚀

[eyalgal]

Wrapped up the first week of our month-long stabilization sprint and call for co-maintainers on the Terraform provider project! 🚀

First and foremost, I want to thank the community for your incredible engagement and trust. We already have several community members actively helping, and more joining soon. We're also identifying internal contributors and planning for the “day after” this sprint, so we can build a robust network of maintainers to keep this project healthy for the long haul.

Highlights from Week 1:

• Released v6.7.0 — our first release since February!
• Closed 28 issues and merged 36 PRs 🎉
• Welcomed 2 new external maintainers who are already contributing
• 2 more maintainers are onboarding and ramping up
• 💥 Huge shout-out to @nickfloyd for the amazing work!

We’ve already completed over 60% of our planned work (milestone progress), with 20 medium-to-significant effort items still open. @nickfloyd is tackling the go-github upgrade, and we’re looking for help with the rest of the milestone’s open issues.

If you’d like to get involved, please comment here, reach out on LinkedIn, or comment/tag me on a specific issue you’re interested in!

Thanks again for your support and have a great weekend! 🌟

[deiga]

Amazing work!

I'd love to offer some of my time to help maintain this. We're very eager to move a lot our Enterprise management from ClickOps to Terraform, so have a vested interest in making the provider better.

I've been a long time Terraform user, have very little experience contributing to a TF provider, but I'm a fast learner :)
GitHub API I'm pretty familiar with and Golang I'm moderately familiar with

[eyalgal]

Hey everyone,

I wanted to give you all a quick and exciting update on our stabilization work. We've made some great strides, with 60 PRs merged and 6 releases so far! A huge thank you to everyone who has contributed and supported this effort.

This past week, progress was a bit slower as @nickfloyd was on-call for another project. I'm happy to report he'll be back with us next week to continue the great work.

We're still looking for more community members to join us as co-maintainers, both for the current stabilization effort and for the future of the project. Your contributions are what make this community so special!

To make collaboration even easier, we've set up a new Slack channel. If you're interested in getting more involved, please send me a message on LinkedIn, and I'll be happy to add you.

Looking forward to continuing this momentum with all of you.

[pascal-hofmann]

Hi @eyalgal,
I’m glad to see that GitHub is putting more attention into this provider. I’m a bit unsure, though, about the call for maintainers. From my perspective, it would be helpful if GitHub could dedicate (more) internal resources to this work - especially since many users (the company I'm working for included) are already paying customers.

Regarding stabilization, we unfortunately haven’t seen improvements yet. In fact, recent releases have included blocking issues that required us to roll back updates twice in the past month. The latest release is also affected, and there is no newer release with a fix nor a pinned warning about the issue. Edit: There is a new release now. 🚀

I also noticed in some recent PRs that a number of test cases look a bit unusual, or that PRs get closed and re-created again. It made me wonder whether AI-generated contributions might be playing a role. Some projects include a brief note in their PR template indicating if - and how - AI was used in creating a PR. Having something similar here could be really helpful in assessing PR quality and determining how deep a review should go.

Cheers,
Pascal

[eyalgal]

Hi Pascal,

Thank you for sharing your perspective and raising these important points!

We completely understand the desire for GitHub to dedicate more internal focus to the Terraform provider, especially given how critical it is to so many users and organizations. Our approach combines internal oversight with active community collaboration: we maintain responsibility for critical updates, security, and API compatibility, while encouraging contributions from the broader Terraform community.

This hybrid model allows the provider to evolve faster, cover a wider range of use cases, and benefit from diverse expertise and real-world feedback that wouldn't be possible through internal effort alone. We are continuing to scale our internal involvement, but community collaboration remains central to the long-term health and evolution of the project.

On your point about recent stability issues and PR quality, we genuinely appreciate your candor. We're aware that rapid release cycles and dependency upgrades can introduce new frictions. Our focus right now is strengthening our testing, CI/CD processes, and code review practices to improve reliability, no matter whether the code comes from a human, Copilot, or any other tool. Copilot is a helpful resource for many contributors, but ultimately, our priority is ensuring every change meets a high standard for quality and correctness.

We're already looking into some of the specific review and test case concerns you mentioned. If you see something that looks off or have suggestions for additional guardrails, we'd love to hear them.

Thanks again for your thoughtful feedback and for helping us make this provider as robust and transparent as possible.

[eyalgal]

Heads up! I've just published a new discussion post covering the latest progress in our stabilization sprint, what's planned next, and a huge thank you to everyone who's contributed so far. 🚀

Check out the full update here - whether you're interested in contributing, following along, or just curious about the direction of the project, we'd love to hear your thoughts and feedback!