Related to #101 , relative links to files in issues should work. Instead, right now, they try to show up as subfiles of issues/. In light of the current behaviour, this is unintuitive and inconsistent behaviour.
As a suggestion, they could also refer to that file within a specific commit with syntax like:
[a link](path/to/file.ext@COMMITHASH)
I think this is a valid point. I've been thinking about how we can make our markup rendering be more similar between issues and READMEs, so any relative links would be to files in the repo.
Not to hop on this issue but @bkeepers if you are thinking about making things more consistent don't forget about the wiki as well. I know that might be more challenging though because Gollum has its own set of assumptions. It would be nice if (test)[test.md] was more similar across READMEs and wikis. Right now that link on the wiki links to the raw test.md file.
+1 would love to see this
A change to the code in this repository can't actually resolve this issue, so I'm going to close this. Thanks for feature request and know that we've heard it.
:+1: I would like to be able to write in an issue
Please see [CONTRIBUTING.md][]
Is this in the wishlist ?
@bkeepers
Just ran into this today, it would be very nice functionality. If this isn't the right repo for this issue, it would be nice to point someone to an identical issue in the right repo.
Now that linking to individual lines in a file works, I've been using that feature instead.
This is awesome:
https://github.com/github/markup/blob/11a355bba9c6d9f25836b9be09262d2362ca9177/Rakefile#L1
The user interface doesn't unfortunately make it very easy to do the same for Markdown files. Because they're rendered prettily, there's no line numbers to click on. The linking still works though:
https://github.com/github/markup/blob/11a355bba9c6d9f25836b9be09262d2362ca9177/README.md#L1
Ahh, interesting. Thanks for the pointer!
Most helpful comment
:+1: I would like to be able to write in an issue
Please see [CONTRIBUTING.md][]