Is there any option to opt-out this thread from mentioned-in-Discourse notification at GitHub? I think these notifications do not really add to discussion there on GitHub (unlike the normal case where extra context can become available on Discourse)
The extension seems pretty limited, and I do agree, I would rather it doesn’t end up notifying on the PRs. This is a thing I didn’t think would happen when writing this.
Could we tweak the plug-in to not trigger the action when there are more than X GitHub links. This would be consistent with how Discourse/GitHub/GitLab (not sure which of these it was) handles mentions.
Unless we start paying for Discourse, we cannot use custom plugins. We could, however, try to integrate a change into the upstream plugin and then benefit from it.
1 Like
Any idea if the plugin currently re-parses messages when they are edited? (possible workaround)
I don’t know, yet.
Let’s see.
Edited in: e2fsprogs: 1.45.4 -> 1.45.5 by samueldr · Pull Request #79198 · NixOS/nixpkgs · GitHub
We now know that it triggers.
1 Like
I guess there is a crazy option of having a redirector on NixOS.org to be able to create links effectively-to-GH that are not recognisable…
Speaking of redirection, we could go with the good old malware’s favorite: the URL shortener.
This is a github.com URL shortener. Depending on if it can be automated or not, it might do the trick
Speaking of redirection, we could go with the good old malware’s favorite: the URL shortener.
Hm true, if it is GitHub-operated then the risk of operational changes is around the same as for GitHub and also correlated, so we do not really make things worse.
Of course, an own redirector could have PR repo&ID in the URL, but maybe it is not worth the extra effort.
This is a github.com URL shortener. Depending on if it can be automated or not, it might do the trick
You mean, depending on whether the plugin learns to auto-expand it?
1 Like