Correct readme for workflows role

[darmach]

Cosmetic changes, whitespace removed, var names fixed.

[gemini-code-assist]

Summary of Changes

Hello @darmach, 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 refines the README.md file for the github role by implementing minor cosmetic and consistency improvements. The changes aim to enhance the documentation's accuracy and readability, ensuring that variable descriptions are precise and example configurations follow established naming patterns.

Highlights

• Documentation Clarity: Removed an unnecessary trailing whitespace character in the description of the github_kayobe_group_id variable within the README.md file.
• Variable Naming Consistency: Updated example variable names in the github_workflows section of the README.md to consistently use the github_ prefix (e.g., build_kayobe_image became github_build_kayobe_image), improving readability and adherence to naming conventions.

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 introduces some helpful corrections to the README.md file for the github role. The removal of trailing whitespace improves code style, and fixing the variable names in the YAML example makes the documentation accurate and prevents potential user confusion. The changes are correct and improve the project.

While reviewing the README.md file, I noticed another minor documentation inconsistency that is outside the scope of the current changes. On line 62, the variable is documented as github_buildx_enable, but in roles/github/defaults/main.yml it is defined as github_buildx_enabled. You might want to consider correcting this in a follow-up pull request to ensure consistency.