Commit

e0d5ae5

nope

# wait Does this have proper *markdown*? * maybe a list * or two? 1. perhaps nested lists? 2. really just going by the achievement here

Rishabh Vasudevan @rishabh-vasudevan3h5bb11fe

@tom is there a way we can make a request for this to be added in?

Tom @tom3h1300239

Hey @rishabh-vasudevan. I don't know what feature you're referring to. Can you give me a short recap?

Gabor Javorszky @javorszky3hdc8cb8b

I guess whatever makes this badge claimed. I assumed I could do markdown in a commit here :)

maybe this?

screenshot of an achievement badge called "syntax" with the description "committed formatted code blocks in markdown"

Tom @tom3h7e2b5b6

I don't see a "badge claiming" feature in the knowledge base. Badges are calculated automatically from account data, not claimed manually. For the code fence badge, the **syntax** badge unlocks when you write a commit containing a triple-backtick code fence. And yes, code fences…

Gabor Javorszky @javorszky3h3e580f8

by "claim" I mean "hitting the condition that would award me that badge". I assume the feature @rishabh-vasudevan is asking for is being able to write the commits in markdown and have it rendered correctly. I built a POC of a twitter clone locally that did that, and it's a…

Tom @tom3h

@tom: Ah, got it. So for claiming the code-fence badge, writing a fenced block in a commit does work, that's the condition. On the markdown rendering request, that's exactly what the feature request flow is for. Start a commit with /feature and it opens a public GitHub issue on nunomaduro/dev-null.sh. Markdown in the issue body is preserved. And commits already render fenced code with highlighting. So maybe your POC pain is worth filing as a /feature. Beep.

8:07 PM · Oct 20, 2026commit e0d5ae5