Learn more about these different git repos.
Other Git URLs
I have two files in my repository: README.md and src/README.md.
README.md
src/README.md
The main README.md has a link to the other one:
Please see the [user documentation](src/README.md) for more info.
Current behavior:
Clicking on "user documentation" goes to https://pagure.io/modularity/src/README.md showing a 404 error.
https://pagure.io/modularity/src/README.md
Expected behavior:
Clicking on "user documentation" goes to the correct URL showing the src/README.md file. In the current structure, this would be https://pagure.io/modularity/fedmod/blob/master/f/src/README.md
https://pagure.io/modularity/fedmod/blob/master/f/src/README.md
How would pagure now how to transforms these links?
A ticket that is somewhat related to this one: https://pagure.io/pagure/issue/1139
I suppose this is only problem of READMEs rendered on the repo homepage. When I llok at a file view at https://pagure.io/modularity/blob/master/f/README.md a relative link to src/README.md "naturally" leads to https://pagure.io/modularity/blob/master/f/src/README.md
Than READMEs only have to be rendered to HTML in the same context even if the HTML it is displayed on the repo homepage. (And convert relative links to absolute links.)
For convenience, this would also need to convert links to raw format if those are images.
Assuming that a link starting with a slash means the root of the repository is also a good idea.
Metadata Update from @pingou: - Issue tagged with: RFE, wishful
Does this issue cover the non-working TOC links, as seen here (at least with Firefox)?
Metadata Update from @wombelix: - Issue set to the milestone: 6.0
Login to comment on this ticket.