Markdown export: move the emoji to the end of the line

[mhansen]

So that the ## parses as a markdown <h2> heading.

Fixes: #12276

[gemini-code-assist[bot]]

Summary of Changes

Hello @mhansen, I'm Gemini Code Assist[^1]! 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 resolves a markdown parsing issue by adjusting the placement of emojis in exported chat history. Previously, emojis preceding ## headings prevented them from being correctly interpreted as <h2> elements. The change moves these emojis to the end of the heading line, ensuring proper markdown rendering and improving compatibility with markdown parsers.

Highlights

• Markdown Formatting: Emojis are now moved to the end of heading lines in markdown exports.
• Improved Parsing: This change ensures that ## is correctly parsed as an <h2> heading by markdown renderers, resolving a previous issue where leading emojis interfered with parsing.
• Affected Files: The chatCommand.ts file, responsible for markdown serialization, and its corresponding test file chatCommand.test.ts were updated to reflect this change.

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 :thumbsup: and :thumbsdown: 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.

[^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.

[mhansen]

Unrelated tests seem to have failed; I rebased my branch to retry the tests and now I need approval again, my approval is outdated. @scidomino can we try approving again?

[mhansen]

Thank you Tommaso and thanks for pushing a commit to fix the test (sorry if I missed a test!)

On Thu, 4 Dec 2025 at 10:43, github-merge-queue[bot] < @.***> wrote:

Merged #12278 https://github.com/google-gemini/gemini-cli/pull/12278 into main.

— Reply to this email directly, view it on GitHub https://github.com/google-gemini/gemini-cli/pull/12278#event-21345335923, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAZYOPXQKV3U3NPUGH332D375YS7AVCNFSM6AAAAACKT2TB4OVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMRRGM2DKMZTGU4TEMY . You are receiving this because you modified the open/close state.Message ID: @.*** com>