http://example.com
http://<span></span>example.com
http://example.com
http://<span></span>example.com
Did some more poking around for options that wouldn't noticeably affect formatting- the one that seems to work on everything I've tried is embedding ‌
(zero-width-non-joiner)- used for controlling ligature behavior, so should be a no-op in most interesting cases that get auto-linked with URLs, PR numbers, etc.
https:‌//example.com
-> https://example.com
ansible/ansible#‌83065
-> ansible/ansible#83065
We got nailed by this recently when a file size in a release note ended up mapping to a shortened commit SHA.
GitHub appears to block most URL schemes for links. It's quite possible that
http:
andhttps:
are the only URL schemes that GitHub will actually allow, which makes sense for security reasons.Even if you attempt to make this link using direct HTML tags instead of Markdown link syntax to explicitly create that hyperlink, it still doesn't work because the forbidden URL scheme still causes the explicit hyperlink to be stripped out of the text:
This still renders as plain text: Storage Settings
It appears that the only effective workaround would be to render the forbidden URL as plain text and instruct the reader to copy/paste it to their browser URL bar to open the link, like this:
It's not as convenient for the user as a hyperlink, but it still offers a way to reach the intended destination!