Bump integrations/github to v6

[priteau]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @priteau, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the integrations/github Terraform provider to its latest stable version. This upgrade is crucial for maintaining compatibility, accessing new functionalities, and benefiting from performance improvements and security patches offered in newer releases.

Highlights

• GitHub Provider Version Bump: The integrations/github Terraform provider has been updated from version 4.28.0 to 6.11.1 in terraform/github/provider.tf.

Changelog

• terraform/github/provider.tf
  • Updated the github provider version from 4.28.0 to 6.11.1.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the integrations/github Terraform provider from version 4.28.0 to 6.11.1. This is a major version upgrade that introduces significant breaking changes that are not addressed in this PR. The current Terraform configuration will fail with this new provider version. I've added a critical comment on the version change, detailing the necessary changes in other files (repositories.tf, branches.tf) to make the configuration compatible with version 6.x of the provider. These changes must be implemented for the Terraform apply to succeed.

[stackhpc-ci]

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Validation Output

Warning: Deprecated attribute

  on repositories.tf line 19, in resource "github_repository" "repositories":
  19:       has_downloads,

The attribute "has_downloads" is deprecated. Refer to the provider
documentation for details.
Success! The configuration is valid, but there were some validation warnings
as shown above.

Terraform Plan 📖success

Show Plan

undefined

Pusher: @priteau, Action: pull_request, Working Directory: ``, Workflow: Terraform GitHub

[priteau]

Need to review the proposed Terraform changes now.

[priteau]

/gemini review

[gemini-code-assist]

Code Review

This pull request updates the Terraform configuration to be compatible with version 6 of the integrations/github provider, migrating github_branch_protection resources and ignore_changes lifecycle hooks. However, there are critical security concerns: the private and default_branch attributes were removed from the ignore_changes list without being explicitly defined, which could lead to private repositories being accidentally made public and default branches being reset to main. Additionally, I've noted significant code duplication in terraform/github/branches.tf and suggest moving the new repository configuration change to a separate PR for better focus.

[gemini-code-assist]

The private attribute was removed from the ignore_changes list in the github_repository resource. Since the private attribute is not explicitly set in the resource configuration, Terraform will default it to false (public). This could lead to private repositories being accidentally made public during a Terraform apply. Although visibility is still ignored, the GitHub provider will still send an update for the private attribute if it is not ignored, which will change the repository's visibility on GitHub.

[gemini-code-assist]

The default_branch attribute was removed from the ignore_changes list. Since it is not set in the resource configuration, Terraform will default it to main. This could cause Terraform to change the default branch of repositories that use a different branch name (e.g., master, devel), potentially breaking CI/CD pipelines and developer workflows.