GitHub starred-repo sync

GitHub stars are a strong signal of which projects you care about. The starred-repo sync feature mirrors your public stars into DevUpdate.io as tracked sources, so when one of those projects ships a new release, you see it in your dashboard and digests without ever pasting a URL.

Overview #

• What it does: fetches your public starred repositories from GitHub and creates a tracked source for each. Un-starring a repo on GitHub deactivates the corresponding source on your next sync; re-starring reactivates it.
• What it doesn't do: it does not access private stars or any data beyond your public star list. Only public repositories are synced.
• When it runs: on-demand only. Click Sync from GitHub stars in the dashboard Sources tab, or Sync stars in the settings card.
• Cooldown: the GitHub-hitting preview is limited to one call every five minutes per user.

Setting it up #

Starred-repo sync requires connecting GitHub via the DevUpdate.io GitHub App. The same connection also powers private-repo lockfile syncing. Your access to a repo is verified using GitHub's own permission model, against your own user token, so DevUpdate.io can never see a repo you don't already have access to on github.com.

1. Open Settings → GitHub connection.
2. Click Connect with GitHub. You'll be redirected to GitHub's consent screen, where the DevUpdate.io GitHub App asks for read-only access to your email addresses and to the contents and metadata of repositories you select. No write permission is requested anywhere. Public-repo starred sync works as soon as you authorize. You can revoke access any time from github.com → Settings → Applications.
3. (Optional, only needed for private stars / private lockfiles.) Install the DevUpdate.io GitHub App on your user account or org via the Install on a repository link on the settings card, and pick which private repos it can see. Authorizing alone doesn't grant private-repo access; the per-repo install is what unlocks it.
4. Back on the settings card, click Sync stars to run the first sync.

DevUpdate.io previously used a single shared OAuth App for all GitHub access. The current flow uses a per-user OAuth connection (so GitHub itself attests to every repo-access decision) plus a separate organisation GitHub App (which handles the recurring fetches under a read-only install on the repos you choose). If you signed up under the old flow, the Connect with GitHub button re-prompts you through the new one: accept once and you're set.

How sync behaves #

Every sync compares your current GitHub stars to the sources we've previously created on your behalf and produces three buckets:

• Adds: newly starred repos that aren't tracked yet, created as new sources.
• Reactivations: previously-synced repos that you un-starred and then re-starred, toggled back to active.
• Deactivations: previously-synced repos that you un-starred, toggled inactive (we never delete them, so no analysis history is lost).

The diff respects two important sticky rules:

• Manual deactivation sticks. If you turn off a starred-sync source by hand, re-running the sync leaves it alone, even if the repo is still in your stars. The pause survives across syncs until you re-enable it manually.
• Other sources are never replaced. If you already track a repo via a manual add or a lockfile, sync skips it instead of replacing the discovery metadata.

Picking which stars to track #

If you have more incoming stars than your plan's source cap allows, the sync opens a picker so you choose which to track. The picker shows a count of remaining slots ("Selected 3 of 5 available slots") and a link to upgrade for unlimited sources. New adds and reactivations share the same slot budget; un-stars deactivate automatically regardless of what you pick.

If you re-run sync later, any starred repos you didn't pick the first time will appear in the picker again; you can swap them in by re-selecting.

Tier limits and downgrades #

Starred-sync sources count toward your tier's source cap exactly the same as manually-added or lockfile-discovered sources.

When a plan downgrade forces deactivation of excess sources, DevUpdate.io keeps your manually-curated sources first and deactivates starred-sync rows before any manual ones. Manual adds are the strongest intent signal; starred sync is trivial to re-create by re-running the sync after upgrading.

Privacy #

We only access your public star list. See the privacy policy for the full data-handling statement covering starred-repo sync.