Hi hyperpolymath 👋

+1 — excellent feature request! This is exactly the kind of small-but-impactful improvement the AsciiDoc community has been waiting for.

GitHub already renders .adoc files perfectly everywhere (README.adoc shows up beautifully in the repo view, and AsciiDoc is fully supported in the markup renderer). The only missing piece is the Community Standards / Community Profile checklist on the Insights page — it still only looks for the .md versions of:

• CONTRIBUTING.adoc
• CODE_OF_CONDUCT.adoc
• SECURITY.adoc
• SUPPORT.adoc
• etc.

Projects that standardise on AsciiDoc (Fedora, Spring, Eclipse Foundation, Asciidoctor ecosystem, many enterprise repos, etc.) are forced to maintain duplicate .md files just for the green checkmark. That’s unnecessary friction.

Why this should be prioritised

• GitHub already knows how to parse .adoc (same Asciidoctor engine).
• The health files logic is already flexible for .md / extensionless / .txt.
• Extending it to .adoc would be a tiny backend change with huge benefit for documentation-heavy projects.

Current workaround (until implemented)

Keep both versions side-by-side or accept an incomplete health score — neither is ideal.

GitHub team — this one is a no-brainer. It aligns perfectly with your existing AsciiDoc support and would make thousands of repos happier instantly.

Upvoted and following! 🚀

Anyone else using AsciiDoc as their primary format? Drop a 👍 below so we can show the demand.