silverwind

> Well… That does have a major drawback though, @silverwind: If I understand your proposal correctly, it means we have to hardcode HTML into a comment. I am not a...

> And it will not highlight references which are not valid at commit time. I see that as a nice side-effect that one can not link into the future. Either...

On the other hand, existing instances with thousands of issues would not benefit from a fix that is done at commit/comment time, so likely doing it purely at render time...

We could at least detect the 404 and show "It looks like this issue does not exist", that'd at least get the ugly error away as a temporary solution.

https://github.com/go-gitea/gitea/pull/31181 will not render the popup completely on non-existant issue, so after that, the only remaining task would be to not linkify these nonexistant issues in first place on backend.

Do we have other places where we can re-use that new subtemplate? I think commit graph likely has similar tags, but with a border there (I think I like a...

Thanks, it does need some style adjustments, the icon makes it too big. Can check later, maybe remove icon. Also I wonder what the significance of the blue border is.

https://github.com/go-gitea/gitea/pull/31160 will rewrite the commits table and make a lot of space for this, so I think we should wait on that to land here.

What's weird? Looks as expected. There is not enough space to render all so it moves the overflow into "...".

Hmm yes, there was no space there in 1.21, likely a small visual regression.