How to Customize GitHub Feeds to Reduce Noise and Show More Relevant Activity?

[1336052171]

Select Topic Area

Question

Body

I’m starting a new discussion about GitHub Feeds and the Feeds API. Recently, my dashboard feed has become increasingly noisy due to activity from large organizations, automated bot events, and repositories I only occasionally follow. I want to better curate the feed so that it highlights the activity that truly matters to me.

I’d really appreciate insights on the following:

Is there a way to filter or prioritize specific types of events in the GitHub feed?
For example: only PR updates, only stars from followed users, or only activity from selected orgs.

How customizable is the Feeds API for building a personalized dashboard?
Are there recommended ways to fetch and sort events by relevance, type, or user?

Can unwanted activity (e.g., bot commits or automated workflows) be hidden or minimized in the default feed?
get6.biqyf.com
Has anyone built tools or scripts that layer additional filtering or ranking logic on top of the Feeds API?
I’d love to hear about your setup.

For teams: How do you structure feeds so developers only see meaningful updates across shared repositories?

GitHub Feeds are powerful, but without good filtering they can become overwhelming. Any tips, workflows, or examples from your experience would be very helpful.

[yassine-krichen]

There are a few ways to bring more control and signal-to-noise to GitHub Feeds, but the options vary depending on whether you’re using the default UI or the Feeds API.

1. Filtering or prioritizing event types in the default feed

The built-in dashboard feed is not fully configurable today. You can:

• Unfollow repositories or users whose activity you don’t want to see.
• Turn off notifications for specific repos or event types.
• Disable “Watch” on repositories that generate too many updates.

However, the dashboard feed itself does not currently support granular filtering like “only PR updates” or “only stars from users I follow.” That level of filtering requires using the API.

2. Using the Feeds API for a personalized dashboard

The Feeds API gives you endpoints for:

• Events for the authenticated user.
• Events for specific repos, orgs, or users.
• Public events.

From there, you can filter client-side on:

• type (e.g., PullRequestEvent, PushEvent, WatchEvent)
• actor.login (to filter by user)
• repo.name (to include/exclude orgs or projects)

Most people use:

• A simple backend script (Python, JS, Go)
• Or GitHub Actions + a static page

Then they filter, sort by timestamp, and display only what matters. This gives you the “custom feed” GitHub doesn’t offer in the UI.

3. Minimizing bot or automated activity

Bots and workflow-generated events are just regular events with:

• An actor whose username ends with [bot]
• Or an event type like WorkflowRunEvent / CheckRunEvent

With the API, you can easily drop them:

if (event.actor.login.endsWith("[bot]")) skip;

In the web UI, hiding bot noise isn’t possible globally, but you can reduce it by adjusting “Watch” settings on noisy repos.

4. Tools people commonly build on top of the Feeds API

Typical setups others have shared include:

• A custom dashboard aggregating only PRs opened by your team.
• A script that sends filtered digest emails or Slack messages.
• A browser extension that hides unwanted events in the GitHub UI.
• A local CLI tool that fetches events and surfaces them by priority.

Tools aren’t officially provided by GitHub, but the API is flexible enough to support this.

5. Team workflows

Teams I’ve seen often:

• Maintain a team “watchlist” of repos and fetch only those events.
• Filter events to just PullRequestEvent, IssuesEvent, and ReleaseEvent.
• Send a daily or weekly curated feed into Slack or Teams.
• Use code owners or review tools as the primary signal source, and keep feeds as a secondary channel.

---

Summary

• The default GitHub dashboard feed is intentionally simple and not highly customizable.
• The Feeds API gives you the control you need: filter by event type, user, org, exclude bots, and build a personalized dashboard.
• Many developers create lightweight scripts or dashboards to get a focused signal instead of dealing with raw GitHub feed noise.

[iyawnnn]

With all the noise from big companies, bots, and repos you don't follow carefully, the GitHub feed might be too much to handle. You can't filter very well using the built-in choices, but you can put specific sorts of activity at the top of your dashboard, such PR updates or stars from individuals you follow. You can filter events by type or user with the Feeds API, but you will need to write some own code to achieve this. You may use it to make a custom feed that only shows you the activities that matter to you, leaving out things like bot commits and automatic workflow events.

You may make your own dashboard with the Feeds API if you require greater accuracy. You can then sort and filter events anyway you like. Some individuals have also made programmes that provide more filtering on top of the API to assist cut down on the noise.

For teams, creating distinct channels or notifications for certain events, such PR comments or commits, can help keep the feed on track.