Like many others it seems (for example here [0], or this issue [1] that amusingly seems to think it's a problem caused deliberately by the VSCode developers), I have been wondering why this recent change has occurred in GitHub's activity feed and whether there was a way to disable it.
The linked thread provides both some insight into the first question (from a GH product manager who explains the dubious case for including unwanted information in the main feed), as well as a number of hacks and workarounds to resolve the second one (using Block element in uBlock Origin with ##div.release as suggested by ozon2 seems to work perfectly).
I would be interested to hear what others here think about the proposed change in direction for the activity feed (i.e., to make it more about "news from your wider network" rather than "notifications you have intentionally signed up for").
The linked thread provides both some insight into the first question (from a GH product manager who explains the dubious case for including unwanted information in the main feed), as well as a number of hacks and workarounds to resolve the second one (using Block element in uBlock Origin with ##div.release as suggested by ozon2 seems to work perfectly).
I would be interested to hear what others here think about the proposed change in direction for the activity feed (i.e., to make it more about "news from your wider network" rather than "notifications you have intentionally signed up for").
[0]: https://github.community/t/release-notifications-from-starre...
[1]: https://github.com/microsoft/vscode/issues/125951