add action repo, rename tooling folders

[beeme1mr]

This PR

• adds a GitHub action repo to the community management tool

Notes

I did a git mv to rename some existing folders. This should have no impact on the permissions but will hopefully make it more obvious where repos/permissions are managed.

[gemini-code-assist]

Summary of Changes

Hello @beeme1mr, 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 integrates a new GitHub action repository into the community management tool, expanding its functionality. Concurrently, it reorganizes existing configuration by renaming several tooling-related folders to enhance the overall structure and readability of the repository's management configuration.

Highlights

• New GitHub Action Repository: A new GitHub action repository has been added to the community management tool, enhancing the project's automation capabilities.
• Folder Renaming for Clarity: Several tooling folders have been renamed to improve clarity and organization, making it more intuitive to understand where repositories and permissions are managed.

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 adds a new action repository and renames two tooling-related configuration folders for better clarity. The changes are straightforward and well-aligned with the goal of improving the structure. I've left one minor suggestion to maintain alphabetical order in a repository list, consistent with other configuration files in the project.

[gemini-code-assist]

For consistency and improved maintainability, it would be best to keep this list of repositories sorted alphabetically. This is consistent with the ordering of repositories in org.yaml.

  - action
  - cli