-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle repos which are no longer desired #10
Comments
don't really want to do anything fancy here. how about we keep a text file of each with the version in the filename.
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. |
Also need
|
More to think about, there's at least three cases to handle:
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. |
But how do we detect this case? Need some kind of local database on which we can do a diff.
The text was updated successfully, but these errors were encountered: