On Sat, Nov 11, 2017 at 01:43:07PM +0000, Stuart Henderson wrote: Hello Stuart,
> From README: > : Fortunately, basic use cases are fairly simple. First, you need to generate > a > : GitHub OAuth token (Settings -> Personal Access Tokens -> Generate New > Token). > : Then choose your use case. > It's currently in Settings -> Developer Settings -> Personal Access Tokens -> > .. Erf. Updated. I wonder what it'll be called next week! > It would be nice to suggest which permissions are actually needed as there > are many possibilities. (But then it would be nice if upstream mentioned > this too :) I'm a bit nervous about this, as GitHub could change the number, or semantics, of the permissions, and then we'd be inadvertently misleading people until we noticed and updated the port (which, on stable, could be many months). [I suspect, but can't be sure, that upstream might have the same reasons for not documenting these things.] Fortunately, although there's quite a few permissions, I found them to be fairly understandable. > : To backup a single repository: > : > : $ github-backup <organization> -N <repo regex> --all -o <output dir> \ > : -t <oauth token> > This would be <user> not <organization> wouldn't it? Good spot! I've pushed fixes to openbsd-wip. Laurie -- Personal http://tratt.net/laurie/ Software Development Team http://soft-dev.org/ https://github.com/ltratt http://twitter.com/laurencetratt
