fix(chat): update WORKSPACE-Context.md with Chat-specific formatting instructions

[kamladi]

Partially addresses
#58 (Chat formatting task).

Testing:

• Manual test: LLM converts **bold** and __bold__ to *bold*
• Manual test: LLM converts *italic* to _italic_
• Manual test: LLM converts [text](url) to <url|text>
• Manual test: LLM flattens nested list items, but prefixes the list items with dashes to indicate depth (e.g., "- parent", "- -- child", "- --- grandchild")

Supported syntax:

- *bold* (single asterisks, not **)
- _italic_
- ~strikethrough~
- `inline code` and ```code blocks```
- Bulleted lists ("* " or "- " at line start)
- Links: <url|display text> (not [text](url))
- User mentions: <users/{user}>

Unsupported syntax (must be converted or avoided):

- **double asterisks** for bold
- # headings
- [text](url) markdown links
- > blockquotes

[gemini-code-assist]

Summary of Changes

Hello @kamladi, 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 WORKSPACE-Context.md documentation by adding comprehensive guidelines for formatting messages specifically for Google Chat. The new section details the subset of Markdown supported by Chat and provides explicit instructions on how to convert unsupported syntax, such as double asterisks for bolding or standard Markdown links, to ensure proper rendering. These updates aim to improve the clarity and consistency of communication within Google Chat when using the Workspace Extension.

Highlights

• New Chat Guidelines Section: A dedicated section for Google Chat Guidelines has been added to the WORKSPACE-Context.md document.
• Chat Formatting Rules: Detailed rules for supported and unsupported markdown syntax in Google Chat are now included, with instructions on how to convert unsupported formats (e.g., **bold** to *bold*, [text](url) to <url|text>).
• Document Readability Improvements: Minor formatting adjustments, such as line wrapping and consolidating code examples, have been made throughout the document to enhance overall readability and conciseness.

🧠 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.

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 adds helpful Chat-specific formatting guidelines to the workspace context document. However, it also introduces widespread formatting changes that reduce the document's readability and consistency by flattening lists into paragraphs. The new Chat Guidelines section contains a couple of small but important errors regarding the syntax for italics and code blocks. My review includes suggestions to fix these errors and to revert the formatting of lists to improve clarity.