Feature request: recognise .adoc (AsciiDoc) for Community Standards health files

[hyperpolymath]

Summary

GitHub's Community Standards tab (the "Community profile" checklist on a repo's Insights page) currently only recognises .md (Markdown) files for community health indicators like CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, etc.

Repositories that use AsciiDoc (.adoc) — which GitHub already renders beautifully — are penalised in the community health score because the platform doesn't detect their .adoc equivalents.

The ask

Please extend the community health file detection to recognise .adoc alongside .md for:

• CONTRIBUTING.adoc
• CODE_OF_CONDUCT.adoc
• README.adoc (already works for rendering, but not always for health checks)
• SECURITY.adoc
• SUPPORT.adoc

Why this matters

AsciiDoc is widely used in enterprise, documentation-heavy, and standards-oriented projects. Many projects (Fedora, Spring, Asciidoctor ecosystem, Eclipse Foundation projects) standardise on .adoc because of its richer feature set (includes, cross-references, conditional content, callouts).

Forcing these projects to maintain duplicate .md files purely for GitHub's community health checklist is unnecessary friction — especially since GitHub already has full AsciiDoc rendering support.

Current workaround

Maintain both .md and .adoc versions of the same files, or accept an incomplete community health score. Neither is ideal.

Thank you for considering this — it would be a small change with outsized impact for the AsciiDoc community.

[notcoderhuman]

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.