JakeWharton
Handle repos which are no longer desired
But how do we detect this case? Need some kind of local database on which we can do a diff.
don't really want to do anything fancy here. how about we keep a text file of each with the version in the filename.
github/owned.1.txtgithub/watched.1.txtgithub/starred.1.txtgit/repos.1.txt
Each is sorted. Then we just do a one-pass zipper diff down the API lists and local lists and delete anything that's removed.
More to think about, there's at least three cases to handle:
- The repo was unstarred/unwatched in which case we want it removed.
- The repo was moved in which case we want to move our local copy as well.
- The repo was deleted in which case we want to do nothing.
For 1 we can still ping the repo on GitHub to confirm it exists in which case we know it was removed. For 2 we should be able to get information from GitHub from that same ping in which case we can move the local repo before the sync occurs (the sync list will already have the new repo in it). For 3, presumably the GitHub ping will 404 in which we do nothing.
The behavior of 3 is annoying for forks in which case you only want to send a PR and then later delete. Not sure what to do about it. That's just GitHub's dumb-ass model of sending PRs.