A matching name is not a connection. In sync means the folder has a .git origin on GitHub. Sync runs git on this server and pushes that folder. The list itself still cannot see C:\ until you sync.
Refresh push times from GitHub (optional)
The token stays in this browser. It is not written to a file on the server. Refresh sends it only to api.github.com. Sync sends it only to sync.ashx on this site, which uses it for that request and does not store it.
Refreshing push times needs metadata read. Sync and Sync new projects need a token that can push and create private repos. A classic token with the repo scope covers that. Anyone who can edit these files on the server could read a token saved here, so use one you can revoke.
How this list was decided
- In sync / Connected. The folder has a .git origin that points at GitHub. On the Nov 5 scan that is only WhereYaHuntin.com and Race The Timer.
- Out of sync / Repo exists, not linked. A GitHub repo matches by name, but the folder has no .git, so commits cannot be compared. That is whereyaeatin, SovHopeExpenseTracking, sblroofing.com, sblprojections, and whereyaflippin.
- Not on GitHub / Local only. On the server, with no matching repo. Never pushed.
- GitHub only. Pathways is on GitHub and had no matching folder.
Scanned C:\OpenCode, C:\Grok Bot, IIS sites outside those roots, and the eight private repos under bqschwarting. Backups, _archive folders, and anything named Secrets were left out. Git is installed on the server but was not on PATH. The scan still read .git folders.
List edits stay in this browser, on top of that scan. Sync is separate: it runs C:\Program Files\Git\cmd\git.exe for one folder at a time. It never force-pushes. New repos are created private. Folders outside C:\OpenCode and C:\Grok Bot are refused unless they are already in the Nov 5 scan.