Group dependabot updates to reduce repo noise

[jbampton]

https://docs.github.com/en/code-security/tutorials/secure-your-dependencies/optimizing-pr-creation-version-updates#grouping-related-dependencies-together

refs apache/shiro#2621

Example Shiro dependabot file at the bottom they are using "groups"

https://github.com/apache/shiro/blob/main/.github/dependabot.yml

https://github.com/apache/sedona/blob/master/.github/dependabot.yml

Only just got this merged for the pre-commit updates in the last day on Shiro and Sedona.

I forgot to add the groups to my last mgem-list PR.

[gemini-code-assist]

Summary of Changes

Hello, 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 enhances the Dependabot configuration by implementing dependency grouping. The primary goal is to streamline the update process and minimize repository noise by combining multiple dependency updates into fewer, more manageable pull requests. This change applies to GitHub Actions, pre-commit hooks, and other general GitHub dependencies, making it easier to track and review security and maintenance updates.

Highlights

• Dependabot Grouping: Introduced groups configuration to the Dependabot setup, consolidating updates from different package ecosystems into a single group.
• Reduced PR Noise: Configured Dependabot to group updates for github-actions, pre-commit, and general GitHub dependencies under a common github-dependencies group, aiming to reduce the number of pull requests generated.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• .github/dependabot.yml
  • Added a groups section to the github-actions package ecosystem configuration.
  • Added a groups section to the pre-commit package ecosystem configuration.
  • Added a groups section to the default package ecosystem configuration.
  • Defined a github-dependencies group with a patterns entry of * for each package ecosystem to include all related dependencies.

Activity

• No specific activity (comments, reviews, etc.) was provided in the context for this pull request.

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 correctly implements grouping for dependabot updates to reduce repository noise. However, using the same group name for different package ecosystems will lead to identically titled pull requests, causing confusion. I've added suggestions to use unique and descriptive group names for each ecosystem to improve clarity.

[gemini-code-assist]

For clarity, it's better to use a group name that is specific to the package ecosystem. Using the same group name github-dependencies for bundler, github-actions, and pre-commit will result in pull requests with identical titles (e.g., 'Bump the github-dependencies group'), making it hard to distinguish between them. I suggest using a more descriptive name like bundler-dependencies here.

      bundler-dependencies:

[gemini-code-assist]

To avoid confusion with other dependency groups and to generate more descriptive pull request titles, I suggest using a more specific name for this group, such as github-actions-dependencies.

      github-actions-dependencies:

[gemini-code-assist]

To make the pull request titles for pre-commit updates more descriptive, I recommend changing the group name to something specific to this ecosystem, like pre-commit-hooks.

      pre-commit-hooks: