Why i am seeing releases from repos that i didnt subscribed?

Recently i have been seeing lots of releases on my feed from the repos that i never subscribed, anyone knows why this is happening?

I never subscirbed to fastapi:

3 Likes

:wave: It looks like you starred it:

https://github.com/gautamkrishnar?tab=stars&q=&q=fastapi

1 Like

@canuckjacq thanks for the reply. Was this introduced recently? AFAIK i will get the releases on my feed only if i check this checkbox:

I also have tons of other repos i have starred gautamkrishnar (Gautam krishna R) / Starred · GitHub, why the release from those are not showing up on my feed? Eg: Releases · sorry-cypress/sorry-cypress · GitHub

Hi Gautam! I’m a product manager at GitHub who works on our activity feed.

AFAIK i will get the releases on my feed only if i check this checkbox

The activity feed is more of a ‘news feed’ to help people discover interesting things happening within their wider network. We currently use people you follow and some of the repos you star (depending on whether we think the event is high quality enough) to determine what we show you. We don’t use watching as a signal as we see the news feed as distinct from ‘notifications’. But we are currently in the process of iterating on these algorithms and learning from feedback from folks such as yourself to determine what works best – so thanks again for your feedback!

Would you be ok to share some more screenshots of your activity feed? Are you finding that releases from repos you’ve starred aren’t interesting to you? And if so why not?

Thanks!

2 Likes

@lukehefson, here’s an item from my feed:


@seek-oss-ci
seek-oss-ci released @vanilla-extract/webpack-plugin@1.0.1 of seek-oss/vanilla-extract 8 days ago

@seek-oss seek-oss / vanilla-extract
@vanilla-extract/webpack-plugin@1.0.1

Patch Changes

  1. 8 days ago isn’t a link, very much unlike every other GitHub view I can think of
  2. There’s no indication why I’m seeing it (which is @gautamkrishnar 's complaint) – the reason something is visible should be easily discoverable / determinable, this isn’t.
    • At this time, I am not watching anything / don’t have anything starred.
  3. I use :star: to bookmark repositories to eventually :fork_and_knife: (why isn’t there a :fork: emoticon :interrobang:). When I get around to them, I fork them, unstar the repository, :hocho: their tags & branches, fork that, and then run check-spelling on the result, and then iterate until I have a PR that I can send upstream.
    It isn’t because I’m interested in their development

I’m picking on them randomly, they happen to be the first such item in my list that isn’t:

  • The first commits to a repo I newly created in an organization I’m in (after I pushed the initial import) – I presume these will stop appearing eventually, but, it isn’t obvious, and it worries me that maybe I’m accidentally watching this newly created repository.
  • check-spelling – an org I own (where I do a lot of forking).
  • people following me (I don’t know why anyone would do that)
  • someone spamming my wiki page :exclamation: :


    daiduongtruong
    created a wiki page in check-spelling/check-spelling 11 days ago

  • someone :star:ing one of my many forks (e.g. jsoref/github-docs) – why?!
  • someone :fork:ing jsoref/spelling instead of check-spelling/check-spelling – which means I need to spend some time doing some SEO (it’s on the todo list)

it’s just a portable ToDo list :spiral_notepad:. It doesn’t require me to sync my browsers across an infinite number of devices.

No, I really don’t care about releases. If I cared, about releases, I’d want to watch the releases page, or have an option in :eye: to watch releases.

Hey @jsoref

  1. 8 days ago isn’t a link, very much unlike every other GitHub view I can think of

Agreed. It’s something we’d like to be able to fix up in the future to make the feed more like other views.

There’s no indication why I’m seeing it (which is @gautamkrishnar 's complaint) – the reason something is visible should be easily discoverable / determinable, this isn’t.

Very much agreed. Our current infrastructure doesn’t allow us to surface better reasons for showing events in the feed. This is something that we know users care deeply about and it’s one of the reasons we’re currently investing in writing new infrastructure for the feed. So pleases watch this space!

Thanks for all your other feedback on the activity feed – I’ll pass it onto the team!

1 Like

Thanks a lot for your replies @lukehefson and @jsoref.

Yep i totally agree with @jsoref in the following point:

  • I use starring as a method of showing appreciation to the projects I like. It will motivate a lots of developers if they are getting enough stars. More stars means more people are interested in your project, they found it useful enough to give it a star. When i star. a repo It doesnt reallly mean that i want to recieve consistant updates about that project. Especially on my news feeds.

  • I personally beliveve that adding a seprate option under the watch button to watch the releases should be enough for people who just want to watch a repo’s releases.

  • If a person really want to watch a project’s releases he should get the update of all the releases no matter what, on his feeds. It shouldnt be filtered by machine learning or collaborative filtering algorithms.

  • Even right now most people are reluctant to starring a repo even if they use that project on a daily basis. Most people dont even know the purpose of the star button on GitHub. Right now change will be a yet annother reason for most open source devs not to recieve the stars on their projects that they deserve. People wont star the repos even if they use the project since their news feed is getting cluttered.

  • Predominantly stars only served as a single purpose which is determining the popularity of a github repo. Trending repositories on GitHub today · GitHub works mostly on stars count. Making it to show something on a news feed would be a really bad idea in my opinion.

  • If you guys are really planning to ship this feature, please add an option to opt out of it

As requested following is the pdf of my feed: https://siasky.net/_Am6hiwJm5r-UJLyfGdyoBfO9Xu_PhUAMyjwk9uFNn1Z6A

I do agree on what @gautamkrishnar 's point.

  1. Star gives a developer a bit of pleasure. It feels kinda like a reward that other developer liked his/her project.
  2. The watch feature was working fine for this monitoring.
  3. Another issue that I find is my feed is getting lot cluttered now with releases.

Possible Solution:

  1. On giving star an option to ask for various watch options
  2. Or the previous star function was fine too.
2 Likes

I never like advertising insertion. Revert this annoying change right now!

I should note that there’s one other expected use from my perspective:
:star: s on repositories impact their appearance in the GitHub Actions Marketplace.

So

cares about :star:s. Although, only barely, as it doesn’t sort by :star:s:

And to the extent that I’m using an action and I want people to be aware that I am, I may leave a :star: on an action (in practice, I hadn’t even :star:'d my own check-spelling action until just now – which takes it to 50 :star:s).

@gautamkrishnar Do you use web notification at https://github.com/notifications as well? As I’m interested to know how you consume GitHub alerts more generally. As I mentioned before we want to move towards making the activity feed more of a space for ‘news’ as opposed to a place where we notify you on every event you subscribe to (and therefore take some sort of action).

I don’t think the activity feed does a very good job of News right now – but it’s something that we’re working to improve!

  • Even right now most people are reluctant to starring a repo even if they use that project on a daily basis. Most people dont even know the purpose of the star button on GitHub. Right now change will be a yet annother reason for most open source devs not to recieve the stars on their projects that they deserve. People wont star the repos even if they use the project since their news feed is getting cluttered.

I completely agree that stars should be used to show appreciation to projects. And that’s something we actually hope to make better by making the activity feed more of a place for News – which the viewer can show their appreciation for by starring or reacting in a positive way. Our hope is that we’ll continue to refine the way we surface events to people and give them new, manual filters in the future so that the can customise their feed in such a way that the feed becomes a great place to discover news and give recognition.

If you guys are really planning to ship this feature, please add an option to opt out of it

There’s no plan to add a general opt-out right now. But in the near future – as we improve the feed – we plan to add manual filters which would allow you to opt out.

1 Like

I mostly use notifications to get important notifications such as Pull requests or issues on my own personal projects. I never usually watch any other projects.

What i will miss out is seeing “x followed you”, “x forked x/repo-name from you/repo-name” and “x starred repo-name”, on my feeds due to it getting cluttered by the release feeds from the thousands of repos i starred. (These feeds usually encourages me as an opensource maintainer to do more open source projects.)

This would be good. I will keep the unwanted feeds filtered away.

2 Likes

I got fucking news again today! Don’t litter the activity with fucking egoistic news!

This is very annoying feature, please revert it.

5 Likes

I’ve starred over 250 repositories for being awesome but I sure as hell don’t want to get notifications for all of them. If I did, I’d be watching them.

5 Likes

There is already “Watch → Releases” functionality. With this new change, you can now have “Watch → Releases” turned off and still be watching releases, which doesn’t make sense to me.

“Watching” and “starring” are separate ideas. “Starring” has been analogous to a like button and I believe this change diminishes the idea of a like button in GitHub.

I’m resisting unstarring many cool repos to not be watching their releases in the hopes that this change will be reverted. Additionally, as a maintainer I am annoyed that doing frequent releases now spams many people who never signed up to watch releases on my repos.

3 Likes

I’m fine with having releases on my github feed. What I’m not fine with is having releases of starred repositories in there. I have hundreds of starred repositories, but I don’t want to follow them.

Some I just find cool, some were helpful at some point but may not be relevant at all to me now (maybe again in the future, but that’s not the point either), some are there as a “hey, need to try this some day”, etc. Stars are used by many as some kind of bookmarks, too. They don’t belong in our feeds; if we want them there we can follow those repositories (maybe add some watch settings on notification vs presence in feed instead?).

I’m (well, was…) a big consumer of my github feed, which is now useless to me since it only contains things I’m not interested about. Please let us change that.

3 Likes

I unstarred core-js repo now because GitHub’s spam is annoying. Count the unstarred repos.

I agree with most in this thread and this change was a bad move. I use the feed to keep up with users and projects I truly care about. What’s perplexing to me is that I’m getting updates for repositories I haven’t watched or starred. In particular, I noticed an update for zloirock/core-js, which I never had starred. My only guess is that Github thought I might want to see the updates because some of my projects may use core-js as a dependency. This is, of course, ridiculous.

1 Like

Well, that would fit with their current view, which I couldn’t agree less with:

The activity feed is an activity feed, allowing us to keep track of what is happening inside our network. Please keep it that way.

1 Like