fix (build): Fix Bazel Steward config git name & email

[vorburger]

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 addresses an issue where the Bazel Steward configuration was not correctly setting the git name and email. The change modifies the .github/workflows/bazel-steward.yaml file to use the --global flag when setting the user.name and user.email in the git configuration. This ensures that the settings are applied globally for the Bazel Steward workflow.

Highlights

• Bug Fix: The pull request fixes an issue where the Bazel Steward's git configuration was not being set correctly.
• Configuration Change: The pull request modifies the Bazel Steward workflow configuration to use the --global flag when setting the git user name and email.

Changelog

• .github/workflows/bazel-steward.yaml
  • Modified the git configuration commands to use the --global flag for setting user.name and user.email on lines 47 and 48.

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.

---

Did you know?

YAML, the configuration language used in the workflow file, stands for "YAML Ain't Markup Language".

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

The pull request updates the Bazel Steward configuration to use global git configuration settings. This seems like a good change to ensure the Bazel Steward has the correct identity when making commits.

Merge Readiness

The code change appears straightforward and addresses the issue described in the pull request title. I am unable to directly approve the pull request, and recommend that others review and approve this code before merging. Given the changes are small and targeted, and there are no critical or high severity issues, the pull request seems ready to be merged after addressing the medium severity issue.

[gemini-code-assist]

Consider adding a comment explaining why --global is necessary here. This will help future maintainers understand the purpose of this change and avoid accidental regressions.

          git config --global user.name "Bazel Steward 🤵" # Use --global to ensure the config is applied for all git operations in the workflow