Revert "fix: add required repository argument for rulesets"

[vedantthapa]

Reverts #64

[gemini-code-assist]

Summary of Changes

Hello @vedantthapa, 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 undoes a previous modification that introduced a mandatory repository argument for rulesets. The change streamlines the ruleset configuration by removing the explicit repository parameter from the ruleset module and its underlying resource, simplifying its usage and reducing boilerplate.

Highlights

• Revert of repository argument: This pull request fully reverts the changes introduced in fix: add required repository argument for rulesets #64, which had added a required repository argument for rulesets. The repository argument is no longer explicitly required or passed within the ruleset module.
• Module ruleset variable removal: The repository input variable has been removed from the modules/ruleset Terraform module, including its definition in variables.tf, its usage in repository_ruleset.tf, and its documentation in README.md.
• Test suite update: Associated tests in repository_ruleset.tftest.hcl that validated the presence and requirement of the repository variable have been removed, aligning the test suite with the updated module interface.

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 reverts a previous change that added a required repository argument for rulesets. While the revert is applied consistently across all files, it appears to re-introduce a critical issue. The repository argument is necessary for creating github_repository_ruleset resources when the Terraform GitHub provider is configured at the organization level. By removing this argument from the ruleset module, creating repository-level rulesets will likely fail in such configurations. I have added a critical comment in modules/ruleset/variables.tf explaining why this revert is problematic and recommending that the original changes from PR #64 be restored.