For the record, I filed a feature request to convert InterTrac links against pagure-importer.

Well, you can reference issues and pull-requests in another project, for example libpagure#12 :)

Is that what you want?

I just fixed a small bug (and hotfixed it) so that linking to project with a '-' in their name works: pagure-importer#50

:)

Yes, that's basically what I want. Ideally, it would

• also work with external pagure instances (trac's interlinks are basically aliases for URLs, similar to git's 'insteadof'
• be properly documented, but that's more something for #1408

Please note that currently there is a minor bug with all these links: The leading whitespace becomes linked, too.

For external instances I think I'm going to drop the ball, at this point it's just as easy to put the full link in there.

Will look if I can fix the leading whitespace.

Thanks for your report :)

Agreed, external links are not that important. Feel free to close this once the whitespace is fixed.

I think it is important to also support full URL references. I personally prefer those because projects tend to be moved from one system to another, e.g. from fedorahosted to github, from github, to pagure, etc... Absolute links are the best you can do to retain consistency.

I think it is important to also support full URL references.

Aren't we already supporting converting URLs to link in comments?

Aren't we already supporting converting URLs to link in comments?

Who's talking about support for displaying links? I'm talking about handling an absolute URL link to a ticket. The first one doesn't seem to work at all so you are apparently using a different syntax from the final display, the second is treated as an ordinary link.

• libpagure#12
• https://pagure.io/libpagure/issue/12

The above two might basically be handled the same way from displaying to control (see excerpt from commit message below).

Closes: https://pagure.io/libpagure/issue/12

The syntax: libpagure#12 works for me :)

I think the issue you are facing is using it in a list, this would need a little time to investigate but I suspect there is a conflict in markdown between the syntax for list and the syntax for links.

Commit 6c7986a fixes this issue

Commit 09cf2c2 relates to this ticket