Rendered intra-project README links are broken

[alilleybrinker]

This issue can be seen here, with the "examples/" link: https://crates.io/crates/finchers

Basically, GitHub allows links to folders and files within the repo, and those links don't work on crates.io. This seems pointy, although I am not sure how best to resolve it.

[joshtriplett]

As a first pass, transforming relative URLs to URLs relative to the repository might make sense.

[kivikakk]

This is tricky; it won't work well in 100% of cases because a repository URL might be something like <https://github.com/kivikakk/blah>, but the URL to a file in that repository is like <https://github.com/kivikakk/blah/blob/master/file.md>.

We can assume that the main branch is master and so just always prepend {repository}/blob/master/ and we'll get the 95% case fixed, which is way better than the current situation (a bunch of broken links).

Edit: of course, this is super GitHub-specific. We could do this only in the case that the repository URL contains ://github.com/, and look up some other patterns for the other big public hosts?

Edit 2: looks like the same style works for GitLab and Bitbucket, so maybe this is OK.

[kivikakk]

A proposal implementing the above is at #1131. There's an ammonia-related caveat I'll see if I can get support from upstream for a fix.

[kivikakk]

This should now be fixed; the example at <https://crates.io/crates/finchers> will be once we rerender READMEs.

[benoittgt]

I have a weird behavior on https://crates.io/crates/git-changelog
Links in the original readme are written like this:

A commit [like this](src/assets/sample-commit.message)

github converts them as

<p>A commit <a href="/aldrin/git-changelog/blob/master/src/assets/sample-commit.message">like this</a>
this</a>.</p>

creates.io generates

<a href="https://github.com/aldrin/git-changelog/blob/master/resources/sample-commit.message" rel="nofollow noopener noreferrer">like this</a>

[carols10cents]

Hi @benoittgt, could you open a new issue please?

[carols10cents]

Actually nevermind, I saw the comment saying "this should be fixed" and thought this issue was closed. This is fine!

[kivikakk]

I'll have a look into this shortly!