Render Mermaid diagrams in Markdown on GitHub Mobile, especially in pull requests

[remiville]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

No response

Body

tl;dr

GitHub Mobile shows ```mermaid blocks as raw source instead of the diagram. Pull requests suffer most: their description and review comments often carry the diagram the reviewer needs.

Contents

Ref	Chapter
T1	Current state
T2	Solution
T3	What does not change
T4	What is expected

Current state

Ref	Element	State
E1	github.com renders Mermaid in PR descriptions, PR comments, issues and Markdown files	ok
E2	GitHub Mobile shows the same blocks as raw source	to change
E3	A PR reviewed on a phone loses its flowchart or sequence diagram, so the reviewer must read the source or switch to a desktop	to change

Solution

Ref	Proposal	Answers
S1	Render ```mermaid blocks in the mobile Markdown view, as github.com does	E2
S2	Start with PR descriptions and PR comments, where the diagram is part of the review	E3

A "View diagram" link opening the rendered diagram would already help as a first step.

What does not change

E1, and the rest of the mobile Markdown rendering.

What is expected

Consideration by the GitHub Mobile team. Related: #197314, which asks the same for repository files on iOS.

Thanks for considering it!

[github-actions[bot]]

Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided.

This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers.