update README.md

[HiGarfield]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @HiGarfield, 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 by standardizing the representation of boolean values. The changes ensure that default settings and example configurations for various parameters are documented using proper boolean literals (true and false) rather than string-encapsulated booleans. This improves the accuracy and readability of the documentation, making it clearer for users to understand the expected input types for the action's parameters.

Highlights

• Documentation Clarity: Updated the README.md to correctly represent boolean default values and example usage by removing single quotes around true and false.
• Boolean Value Correction: Corrected the representation of boolean defaults for ccache, toolchain, skip, clean, and skip_saving parameters from string literals to actual boolean literals.
• Example Consistency: Ensured the example usage for the ccache parameter in the README.md reflects the correct boolean literal true instead of 'true'.

🧠 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

• README.md
  • Updated default values for ccache, toolchain, skip, clean, and skip_saving to use boolean literals instead of string literals.
  • Corrected the ccache value in the example YAML configuration to use a boolean literal.

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 updates the README.md to improve documentation by removing single quotes from default boolean values. This is a good change for consistency and clarity. I've provided a couple of suggestions to further improve the formatting by using backticks for these literal values, which would make them consistent with how other code elements are formatted in the document.

[Copilot]

Pull request overview

Updates the README documentation for the “Cache Wrt Build” GitHub Action, focusing on clarifying input defaults and the example workflow configuration.

Changes:

• Adjusted boolean default formatting in the Inputs section (e.g., true/false).
• Updated the example workflow to use an unquoted boolean (ccache: true).
• Minor formatting cleanup in the README input descriptions.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The phrasing “Check if to …” is ungrammatical and a bit unclear for inputs. Consider rewording to something like “Whether to cache ccache/toolchain. Default …” for readability and consistency.

[Copilot]

Same wording issue here: “Check if to skip …” / “Set to clean …” reads awkwardly. Consider rephrasing these input descriptions to be clear, imperative, and consistent (e.g., “Whether to skip …”, “Whether to clean the cache …”).

[Copilot]

“Skip saving” is a bit ambiguous (saving what?). Consider clarifying what is being skipped (e.g., “Skip saving the cache”).

Suggested change

	Skip saving. Default `false`.
	Skip saving the cache. Default `false`.

[HiGarfield]

@copilot apply changes based on the comments in this thread