I Built a Chrome Extension to hide noisy GitHub Issue timeline events (with Copilot CLI)

Source: Dev.to

What I Built

GitHub Issue Focus is a Chrome extension that hides noisy, automated timeline events on GitHub issues—project shuffles, label churn, assignment ping‑pong, and other bot‑generated chatter.

If you’ve got lots of automation, projects, and/or overly enthusiastic labeling colleagues ಠ_ಠ, you know exactly what I mean. Here it is in action:

Why I Built It

I like my GitHub issues the way I like my sandwiches: simple. No mustard. No mayo. No garnish. No oils. No green stuff. I don’t need five pages of updates showing something moving from Done to Complete and back again.

I’m rarely interested in who applied a label, reassigned an issue, or shuffled it between projects. I care far more about vertical real estate and skimability.

The extension trims the fat so the signal stands out—without removing important context like cross‑references or closed/reopened events. Everything is configurable: hide what you don’t care about, keep what you do.

It works for me—and hopefully anyone drowning in over‑automated issues.

The extension runs automatically on GitHub issue pages. Open an issue, toggle what you want hidden in the popup, and watch the timeline instantly calm down.

If you’ve ever scrolled past 14 consecutive “moved this to Status: In Progress” events just to find a comment—this demo is for you.

(Screenshots or a short GIF of before/after would fit perfectly here.)

My Experience with GitHub Copilot CLI

TL;DR: This was built in under five minutes—and worked out of the gate!

I’ve built a few Chrome extensions before, so I roughly know the territory. I essentially asked Copilot CLI to create this, pasted in some HTML with the offending markup, and was explicit about what should be configurable.

How I used Copilot CLI

• Scaffolded the Chrome extension structure
• Sanity‑checked manifest.json for MV3 correctness
• Generated and refined DOM selectors for GitHub’s issue timeline
• Accelerated repetitive config and test setup

The biggest win was momentum. Instead of context‑switching to docs or Stack Overflow, I stayed in flow—asking Copilot CLI things like “hide GitHub issue timeline events added to project” and iterating from there.

It didn’t replace thinking, but it absolutely replaced yak shaving.

Note: I’m a GitHub employee, so I’ll rule myself out of any prizes. I’d still love the participation ribbon though!