Feature Request: link syntax for external issues

[inexorabletash]

Use case:

In IndexedDB's Revision History section, we link to bugs that tracked changes, e.g.:

* Added {{IDBFactory/databases()}} method. ([Issue #31](https://github.com/w3c/IndexedDB/issues/31))
* Added {{IDBTransaction/commit()}} method. ([Issue #234](https://github.com/w3c/IndexedDB/issues/234))

Note that the numbers are repeated in the link text and url. This leads to frequent mis-linking because humans are squishy.

Bikeshed already has the context to link to the issue tracker, so given an appropriate grawlix around an issue number it could generate the hyperlink automagically.

Low priority. This may be too niche to matter.

[tabatkins]

If a repository has been detected or specified, Issue(123): Inline summary here already works 😀 There's another metadata that determines whether it outputs your summary + a link, it goes and fetched the first comment from the issue.

[tabatkins]

Does this satisfy your use-case?

[inexorabletash]

Issue(123): ... is rendered as a big scary block (at least, with the default stylesheet), whereas my use case is just for a simple link (see the revision history link). So... not really.

But it's a really low priority, probably one-off use case if no one else has asked; I'm fine with "won't fix"

[hober]

Bumping this. I would love to be able to refer to issues in other repositories with GFM syntax, so e.g. https://github.com/privacycg/storage-partitioning/issues/16 could be written privacycg/storage-partitioning#16

[svgeesus]

There's another metadata that determines whether it outputs your summary + a link, it goes and fetched the first comment from the issue.

I know I have seen that in use, but I can't find it in the bikeshed documentation and I can't find an example by browsing the CSS repo.

[svgeesus]

Okay, it is

Inline Github Issues: title