wingetCollections
  • Auto
  • Search
  • Awesome Collections
  • Awesome Programs
  • My Favorite Collections
  • My Collections
  • Account / Settings
  • Terms of Service
  • Privacy
  • About
  • What is WinGet?

© 2026 winget.ragerworks.com

Loading...
Install GitPulse using WinGet - wingetCollections
  1. Go back
  2. Packages
  3. GitPulse
GitPulse logo

GitPulse XxDoomsdayxX

developer-tools electron git github productivity widget
Use this command to install GitPulse with WinGet:
winget install --id=XxDoomsdayxX.GitPulse -e

GitPulse is a compact desktop widget designed to monitor your GitHub repositories and notify you when new commits occur. It stays in the corner of your screen, checking for updates on repositories you follow. When new commits are detected, it alerts you with a red dot and displays how many commits you’re behind. Clicking "Pull" syncs your local clone, ensuring your code remains up-to-date.

Key Features:

  • Real-Time Repository Monitoring: Track multiple GitHub repositories simultaneously, each with its own status indicator.
  • Commit Count Notification: Shows the exact number of commits you're behind, providing clarity beyond a simple "behind" status.
  • One-Click Pull Functionality: Quickly sync your local clone with the latest changes in one step.
  • Folder Verification: Ensures the selected folder is a valid clone of the repository before pulling to prevent errors.
  • Desktop Notifications: Optional alerts notify you when repositories are updated, keeping you informed without switching tabs.
  • Branch Picker: Monitor specific branches, not just defaults, offering flexibility for different workflows.
  • Auto-Updating: Installs updates automatically in the background, ensuring you always use the latest version.

Target Audience and Benefits: Ideal for developers working with GitHub who need to stay updated on project changes without interrupting their workflow. GitPulse streamlines repository management by providing real-time updates and one-click syncing, enhancing productivity and reducing context switches. Available via winget, it integrates seamlessly into your development environment.

README

GitPulse

> A 200-pixel desktop widget that tells you when your GitHub repos have moved ahead of your local clone — and pulls them with one click.

Platform Electron License winget

What it does

GitPulse sits in a corner of your screen watching a list of GitHub repositories. When new commits land on any of them, its dot turns red and tells you how many commits you're behind. Click Pull and it fast-forwards your local clone. When everything's in sync it stays green and silent.

No browser tab. No polling a terminal. One glance.

● 2 repos behind                    ⠿  ×
──────────────────────────────────────────
● gitpulse                      3 behind
● byron-dashboard              up to date
● api-server                     checking…
──────────────────────────────────────────
   + Add repository            ↻      ⚙

Expand any row for the latest commit, its author and age, a branch picker, and per-repo actions.

Features

FeatureDetails
Watch many repos at onceA stacked list, each with its own status, branch and local clone
Commits-behind count"3 behind", not just "behind"
One-click pullFast-forward pull into your local clone, straight from the widget
Folder verificationGitPulse checks the folder you pick is really a clone of that repo before it ever pulls
Desktop notificationsOptional toast when a watched repo moves ahead
Branch pickerWatch any branch, not just the default one
Auto-updateNew versions install themselves in the background
Start with WindowsOptional login-item, launched hidden to the tray
Versions
1.1.0
1.0.1
1.0.0
Website
github.com
License
Last updated
7/24/2026
Download latest version
Loading...
System trayIcon colour-coded to the worst status; right-click for a per-repo summary
Secure token storageYour PAT is encrypted with the OS keychain (Windows DPAPI) and never reaches the renderer
Cheap pollingETag-conditional requests, so unchanged repos cost nothing against your rate limit
DraggablePut it anywhere; position survives restarts and unplugged monitors
No admin requiredInstalls entirely in your user profile

Installation

Option 1 — winget (recommended)

winget install gitpulse

To update later — though GitPulse updates itself:

winget upgrade gitpulse

> Requires Windows 10 1709 or later. winget ships with Windows 11 and is available for Windows 10 via the App Installer.

Option 2 — Installer

Download GitPulse Setup x.y.z.exe from Releases and run it. No admin password needed; installs to %LOCALAPPDATA%\Programs\gitpulse\.

Option 3 — From source

git clone https://github.com/XxDoomsdayxX/GitPulse.git
cd GitPulse
npm install
npm start

First-time setup

1. Create a GitHub token

GitPulse only ever reads. A fine-grained token is recommended:

  1. Go to Settings → Developer settings → Fine-grained tokens
  2. Grant access to the repositories you want to watch
  3. Under Repository permissions, set Contents: Read-only (and Metadata: Read-only, which is implied)
  4. Generate and copy the token

A classic token with the repo scope also works, but it grants read and write to everything you can access — more than this widget needs.

> Your token is encrypted at rest via the OS keychain and is only ever sent to api.github.com.

2. Connect and add repositories

Click ⚙, paste the token, hit Connect. The repository picker opens — search, then click any repo to start watching it. Add as many as you like.

Using the widget

ControlAction
Click the barExpand / collapse the watchlist
Click a repo rowShow commit details, branch picker and actions
PullFast-forward your local clone (asks for the folder the first time)
SeenMark the current remote commit as acknowledged without pulling
⤢ GitHub iconOpen the repo in your browser
🗑Stop watching the repo
+ Add repositorySearch and add another repo
↻Refresh everything now
⚙Settings — account, refresh interval, notifications, start with Windows
Grab the ⠿ gripDrag the widget anywhere
×Hide to the system tray
EscClose picker → close settings → collapse

Status colours

ColourMeaning
🟢 GreenEvery watched repo is up to date
🔴 RedAt least one repo has commits you haven't pulled
🟡 AmberA check failed — expired token, network, rate limit (the row says which)
⬜ PulsingChecking right now

How sync detection works

GitPulse uses the GitHub REST API — it never reads your local .git folder except when you pull.

  1. When you add a repo, its current remote HEAD becomes the "acknowledged" commit
  2. Each poll compares the remote HEAD to that acknowledged SHA
  3. Different → red, with a commits-behind count from the compare API
  4. After a successful pull, the SHA that actually landed locally is acknowledged → green

So the status answers "have I pulled what's on the remote?" — not "is my working tree clean?".

Pull safety: before running anything, GitPulse verifies the folder is a git work tree whose origin points at that exact repository, then runs git pull --ff-only with interactive prompts disabled. A mis-picked folder is rejected rather than silently pulling some other project.

Development

npm start        # run the widget
npm test         # unit tests (settings migration, git handling, GitHub client)
npm run test:app # end-to-end smoke test in a real Electron window
npm run build    # build dist/GitPulse Setup x.y.z.exe

Project structure

main.js              # Main process — window, tray, polling, IPC, notifications
preload.js           # contextBridge — the window.widget API
lib/
  settings.js        # Schema + migration + atomic, debounced persistence
  github.js          # GitHub client — ETags, rate-limit backoff, error mapping
  git.js             # Safe git execution (argv, no shell) and clone verification
  icon.js            # Dependency-free PNG/tray icon generation
renderer/
  index.html         # Markup + CSP
  style.css          # OKLCH design system
  app.js             # Watchlist UI, driven by state pushed from main
test/                # Unit tests (node --test)
scripts/             # Icon generation + Electron smoke test
.github/workflows/   # CI on every push; release + winget submission on a tag

Releasing

Bump version in package.json, then:

git tag v1.2.0 && git push origin v1.2.0

CI runs the tests, builds the installer, publishes the GitHub release, and — when a WINGET_TOKEN secret is configured — opens the winget-pkgs PR.

Roadmap

  • v1.2 — expanded dashboard window: full repo overview, open PRs and issues, recent activity
  • Pull requests welcome.

License

MIT — see LICENSE.

Built with Claude Code