Markup: Render files that looks like markdown that does not have an markdown or md extension.

[AraHaan]

For example I have an markdown file that is named .rst.in which is in input to pandoc to make it generate an rst file. As such github should be able to render it just like the rst file if people go by naming like that.

Example files:
https://github.com/DecoraterBot-devs/DecoraterBot/blob/Async/README.rst.in
https://github.com/DecoraterBot-devs/DecoraterBot/blob/Async/description.rst.in

This can also be said about files that looks like rst as well when used to generate other formats with similar naming strategies. people can name them using the <file name>.<any of pandoc's supported conversion to formats>.in As such I think github should still be able to render those just like the converted ones from pandoc.

However there is a known issue with tables, pandoc likes to ruin them forcing me to convert them to html temporarily just to convert them to rst that looks 100% like the markdown ones.

[kivikakk]

:wave: We do our detection using the linguist gem, so a PR or issue there will be the quickest way to get this fixed.

If you'd like to have a go at fixing this yourself, I can think of two possible routes:

1. You can add the .in variants directly to the extensions key of each format.
2. You could add a heuristic for ".in" which dispatches to the correct parser.

Hope this helps!

[AraHaan]

I think adding an heuristic would work perfectly for this kind of issue.

[AraHaan]

I hate mobile copy of this website as the stupid close and comment button gets in the way of the default iOS keyboard. I think when pressing it GitHub should ask "Do you really want to close this issue after sending this comment?". And then if they press no it would fail to send the comment and not close the issue. Would at least fix the accidential issue close issue of itself.

[kivikakk]

Are you referring to how the "close and comment" button is really near the keyboard here? I'll pass on the confirm dialog suggestion to our UX people! I have closed issues and PRs by accident before too.

[AraHaan]

Yes, but when viewing the extended keyboard on the side the keyboard completely covers the button and sometimes the keyboard disappears while typing and you can accidentally press the button.

[justmehlc76]

Should I render bruising?

Sent from my MetroPCS 4G LTE Android Device

[dexpota]

I managed to get GitHub renders a file without extension as a Markdown file by adding a vim modelines at the top.

<!-- vim: syntax=Markdown -->

To accomplish this I followed the instructions on https://github.com/github/linguist#overrides. I also tried using the override with the .gitattributes file, and I am wondering on why is not working. Any idea?