`sort-conversations-by-update-time`rewrite labels url, making it difficult to get the original one to copy and add in a message about refined-github

[fregante]

It'd be great to use real URLs when posting here, so that I understand what you're talking about, like this:

ajax Temporary label to collect Ajax issues

New feature, neat!

I felt the need to disable Refined GitHub before just to get that exact clean URL, I suppose now there's a real drawback to not using it.

Unfortunately there's no easy way to both have sort-conversations-by-update-time enabled and get that clean URL. We can somewhat fake it in some cases, but I'm generally against the idea of showing the wrong content for the same URL (e.g. if I send https://github.com/refined-github/refined-github/issues to someone and they don't see the same issues I see)

A compromise here would be to clean the URL in the comment fields before sending it, similarly to how we do it with prevent-link-loss — but even that sounds like so much trouble for a rare operation with relatively little improvement.

[fregante]

If you can track down the feedback form for this feature, maybe we can just ask them to support ?q= links too

[Porkepix]

I felt the need to disable Refined GitHub before just to get that exact clean URL, I suppose now there's a real drawback to not using it.

Actually, only untoggling that exact feature is enough to let the url untouched.

Unfortunately there's no easy way to both have sort-conversations-by-update-time enabled and get that clean URL. We can somewhat fake it in some cases, but I'm generally against the idea of showing the wrong content for the same URL (e.g. if I send [https://github.com/refined-github/refined-github/issues](https://github.com/refined-github/refined-github/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc) to someone and they don't see the same issues I see)

I'm not sure I understood that last sentence.

A compromise here would be to clean the URL in the comment fields before sending it, similarly to how we do it with prevent-link-loss — but even that sounds like so much trouble for a rare operation with relatively little improvement.

Same, what do you mean? Especially the urls aren't the same endpoints, so you can't get the url with queries information: with the feature toggled you get a https://github.com/org.repo/issues/ endpoint while without and to show it in comments you need to use https://github.com/org/repo/labels/ endpoint.

If you can track down the feedback form for this feature, maybe we can just ask them to support ?q= links too

I'm not sure what feedback form we're talking about here (don't even know if we can report GitHub issues for things they break, like upload error messages…). But I'd have guessed a repo such as this one would have privileged contacts with their team, though!

EDIT: And what about some kind of "copy URL to this label" button beside it, at least in places it wouldn't be an annoyance, such as https://github.com/refined-github/refined-github/labels ?

EDIT2: I wasn't even sure I remembered correctly about seeing these labels inside messages, and looking for the information wasn't easy, because people asked for this feature for quite some time and found quite a couple of workarounds to get it. Official support seems to have been released without much of an announcement, but you can find https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls#labels found from github/docs#18704 and github/docs#18537