build: Make Bazel Steward group PicoCLI Bump PRs

[vorburger]

So that #1323 + #1324 are a single PR in the future.

Waiting to merge this AFTER #1324 (which is blocked by remkop/picocli#2407 (comment)) is merged, to avoid confusing Steward.

Relates to #254.

[gemini-code-assist]

Hello @vorburger, 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!

Summary of Changes

This pull request modifies the .bazel-steward.yaml file to group PicoCLI bump pull requests. This change ensures that future updates to PicoCLI dependencies, like those previously addressed in #1323 and #1324, will be handled as a single pull request by Bazel Steward. The PR description indicates that this PR should be merged after #1324 to avoid confusing Steward.

Highlights

• Configuration Change: The .bazel-steward.yaml file is modified to include a new group for PicoCLI dependencies.
• Dependency Management: This change aims to consolidate PicoCLI dependency updates into single pull requests.

Changelog

• .bazel-steward.yaml
  • Added a new group-id 'picocli' with dependencies 'info.picocli:*' to the pull-requests section, ensuring that PicoCLI updates are grouped together.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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.

---

A config file's gentle hand,
Guides the Steward through the land.
Picocli's updates aligned,
A single PR, well-defined,
Dependencies now in command.

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 introduces a change to the Bazel Steward configuration to include PicoCLI dependency updates. The change seems straightforward and aligns with the goal of automating dependency management. However, I have a few observations regarding the scope and potential impact of this change.

Summary of Findings

• Scope of Bazel Steward Configuration: The addition of PicoCLI to the Bazel Steward configuration seems reasonable. However, it's important to consider the overall scope of dependencies managed by Bazel Steward and whether this addition aligns with the project's dependency management strategy. It would be helpful to understand the criteria for including dependencies in the Bazel Steward configuration and whether PicoCLI meets those criteria.
• Impact on Bazel Steward PRs: The pull request description mentions that this change aims to consolidate PicoCLI bumps into a single PR in the future. While this is a desirable outcome, it's important to ensure that the Bazel Steward configuration is properly tuned to avoid generating excessive or unnecessary PRs. It would be helpful to understand the expected frequency of PicoCLI updates and whether the Bazel Steward configuration is optimized to handle these updates efficiently.

Merge Readiness

The code change itself is simple and doesn't introduce any immediate correctness issues. However, I recommend considering the broader implications of this change on the project's dependency management strategy and the potential impact on Bazel Steward PRs. It's important to ensure that the Bazel Steward configuration is properly tuned to avoid generating excessive or unnecessary PRs. I am unable to approve this pull request, and users should have others review and approve this code before merging.