You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* add github oauth device flow scaffolding
* switch github api auth to oauth sessions
* replace token setup with github sign in
* update auth errors and disconnect handling
* refresh tests and docs for oauth flow
* fix popup oauth device flow resume
* improve onboarding code copy
* move watched repos to local storage
Chrome sync storage has an 8KB per-item limit which we were hitting with
larger repo lists. This moves watchedRepos to local storage (unlimited
quota) and adds a one-time migration for existing installs.
Also added import validation to enforce the 50 repo limit (unless unlimited
mode is enabled) and better error handling around the import flow.
* fix validation follow-up for oauth branch
* keep ci checks focused on pull requests
* ci: split pull request checks by job
---------
Co-authored-by: jonmartin721 <jonmartin721@users.noreply.github.com>
Copy file name to clipboardExpand all lines: README.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ Monitor pull requests, issues, and releases across multiple GitHub repositories
9
9
10
10
## Key Features
11
11
12
-
-**Guided Setup** - Built-in setup flow for token creation and repository selection
12
+
-**Guided Setup** - Built-in GitHub sign-in flow and repository selection
13
13
-**Browser Notifications** - Get notified about new PRs, issues, and releases
14
14
-**Multi-Repo Monitoring** - Watch up to 50 repositories from one interface
15
15
-**Configurable Updates** - Check every 5, 15, 30, or 60 minutes
@@ -30,7 +30,7 @@ Monitor pull requests, issues, and releases across multiple GitHub repositories
30
30
3. Grant permissions when prompted
31
31
4. Follow the guided setup wizard on first launch
32
32
33
-
**GitHub Token Permissions**: You'll need a [Personal Access Token](https://github.com/settings/tokens/new) with `repo`(for private repos) or `public_repo` (for public only).
33
+
**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.
34
34
35
35
### Manual Installation (For Development)
36
36
@@ -53,7 +53,7 @@ cd devwatch-github
53
53
### First-Time Setup
54
54
55
55
The built-in setup flow walks you through:
56
-
1.Create a GitHub token
56
+
1.Connect your GitHub account
57
57
2. Add repositories to watch
58
58
3. Choose activity types (PRs, Issues, Releases)
59
59
@@ -74,7 +74,7 @@ The built-in setup flow walks you through:
74
74
Filter by type (All/PRs/Issues/Releases), search activities, refresh manually, or browse the archive. Click any item to open in GitHub.
75
75
76
76
### Settings Page
77
-
Manage your GitHub token, watched repositories, activity filters, check interval, notifications, and theme. Export/import settings for backup.
77
+
Manage your GitHub connection, watched repositories, activity filters, check interval, notifications, and theme. Export/import settings for backup.
78
78
79
79
<divalign="center">
80
80
<imgsrc="screenshots/settings-page.png"alt="Settings page for configuring repositories"width="600">
@@ -101,7 +101,7 @@ That said, this project has not gone through a formal accessibility audit or doc
101
101
102
102
## Privacy & Security Notes
103
103
104
-
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, and the current build encrypts the GitHub token before persisting it locally while keeping a decrypted session copy available at runtime.
104
+
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, and the current build encrypts the GitHub auth session before persisting it locally while keeping a decrypted session copy available at runtime.
105
105
106
106
-**Direct network access** - Requests go to `api.github.com`, plus `registry.npmjs.org` only when you use package-name lookup
107
107
-**Scoped browser permissions** - The manifest asks for `storage`, `alarms`, and `notifications`
0 commit comments