devwatch-github

GitHub Devwatch for Chrome

Monitor pull requests, issues, and releases across multiple GitHub repositories from a Chrome extension. It keeps a local activity feed, badge counts, and optional browser notifications without adding another hosted service to the workflow.

Best for people who follow several repos and want one local review queue instead of GitHub email noise, browser-tab sprawl, or constantly checking each repository by hand.

Chrome Web Store License CI codecov

Key Features

GitHub Devwatch - Track your repositories

Requirements

Installation

  1. Visit the Chrome Web Store
  2. Click “Add to Chrome”
  3. Grant permissions when prompted
  4. Follow the guided setup wizard on first launch

GitHub Sign-In Permissions: DevWatch uses GitHub OAuth device flow and requests repo plus read:user so it can monitor private repositories and show the connected account in the UI. The current build uses one sign-in path for both public and private monitoring, so there is not a separate public-only permission mode yet.

Manual Installation (For Development)

  1. Clone this repository 
    git clone https://github.com/jonmartin721/devwatch-github.git
cd devwatch-github
npm install
  2. Load the extension in Chrome:
    • Open Chrome and go to chrome://extensions/
    • Enable “Developer mode” (toggle in top right)
    • Click “Load unpacked”
    • Select the extension directory
  3. Click the extension icon and follow the setup wizard

Quick Setup

First-Time Setup

The built-in setup flow walks you through:

  1. Connect your GitHub account
  2. Add repositories to watch
  3. Choose activity types (PRs, Issues, Releases)
Interactive setup wizard welcome screen

Ongoing Use

How to Use

The popup is the main day-to-day view:

Popup activity feed showing repository updates

Settings Page

Settings are split into a few practical jobs:

Settings page for configuring repositories

Typical Workflow

Here’s what using the extension looks like day-to-day:

  1. A browser notification or badge count lets you know there is new activity.
  2. Open the popup to scan updates across your watched repositories in one place.
  3. Open the item in GitHub when you want to review it, and let DevWatch keep the rest of the queue visible locally.

The extension keeps up to 2000 items in your local history, so you can always check something you saw earlier. Badge count updates automatically as you read items.

Accessibility Notes

The UI includes keyboard navigation, visible focus styles, semantic controls, and ARIA labeling in key flows. The test suite also includes automated axe-core checks and keyboard-focused UI tests.

That said, this project has not gone through a formal accessibility audit or documented screen reader certification. If you run into an accessibility issue, please open an issue.

Privacy & Security Notes

The extension talks directly to GitHub’s API and does not use a separate analytics or sync backend. It stores settings and cached activity in Chrome extension storage, while the current GitHub auth session stays in Chrome session storage so it is not persisted to disk. Legacy encrypted auth data from older builds is cleared when accessed.

Data Storage

The extension stores up to 2000 activity items locally in Chrome storage. This limit ensures the extension stays performant while providing plenty of history.

Feed Management

You can optionally configure automatic expiry of old items:

Items are automatically removed when they exceed the 2000 item limit (keeping the most recent) or when they’re older than your configured expiry time (if enabled).

Rate Limiting

GitHub gives authenticated users 5,000 API requests per hour. Each repo check uses 1-3 requests, so even checking 50 repos every 15 minutes keeps you well under the limit.

The extension defaults to checking every 15 minutes. You can change this to 5, 30, or 60 minutes in settings. The default 50-repo limit is there to keep rate usage predictable, but Advanced settings also let you enable unlimited repositories if you want to trade more flexibility for more rate-limit risk.

Development

Project Structure

/devwatch-github
  /icons                  # Extension icons in various sizes
  /popup                  # Popup interface
    /controllers         # Popup business logic
    /views               # Popup view components
    popup.html
    popup.js
    popup.css
  /options                # Settings page
    /controllers         # Settings business logic
    /views               # Settings view components
    options.html
    options.js
  /shared                 # Shared utilities
    /api                 # GitHub API integration
    /ui                  # Shared UI components
  background.js           # Service worker for background tasks
  manifest.json           # Extension manifest (Manifest V3)

Technologies Used

Running Tests

npm run lint
npm run typecheck
npm test
npm run build

The automated checks cover shared logic, UI behavior, and a range of mocked extension flows. They do not replace manual testing in Chrome for permissions, service worker lifecycle behavior, or end-to-end interactions against live GitHub data.

Jest enforces minimum global coverage thresholds of 47% lines, 46% branches, and 44% functions. That is a floor for the suite, not a claim of exhaustive coverage.

Local Development

  1. Clone the repository
  2. Run npm install for dependencies
  3. Load as unpacked extension in Chrome
  4. Make changes and reload the extension from chrome://extensions/

Contributing

Contributions welcome! Submit issues or pull requests. See CONTRIBUTING.md for guidelines.

How to Contribute

Documentation

Roadmap

This is an actively maintained side project. Some features under consideration:

If any of these sound useful, open an issue or submit a PR!

License

MIT License - see LICENSE file for details.

Copyright (c) 2025 Jonathan Martin

Support

GitHub Devwatch logo
This site is open source. Improve this page.