Backuping up multiple repositories but not the whole account

[McNetic]

I'd like to back up multiple repositories from my account, but not the whole thing, as I have forked various big repositories I just made some small (or no) contributions to. I found no way to to this out of the box, as it is only possible to select a single repository for backup.
Calling the program multiple times with different repositories and the same backup directory does not work either, as the last_update state is not tracked per repository, but only once in the backup directory root.

Would you agree on fixing this, either by making it possible to give multiple repositories to backup, or by moving the last_update state into the repository directory in the backup dir (or preferably both)? I'd be willing to provide pull requests for at least a part of the proposed changes.

[josegonzalez]

Both seem reasonable and can be done separately I think? Pull requests welcome!

(I won't be working on this as the project works fine for my use-case).

[Iamrodos]

@McNetic are you still after this feature?

migrating last_updated to the repo directory is the neat solution. However maintaining backwards compatibility is important. There are some ways to do that whilst allowing repo based last_updated too, but it gets a little messy. If that was done I would suggest a deprecation notice in the logs and documentation that last_updated is going to only be repo based in a year or something and do a major version update when removing it. But you would have to convince @josegonzalez of supporting that.

[josegonzalez]

Probably lets track a per-repository backup file or something and call it a day? Fine if we break BC between releases imo.

[Iamrodos]

Having state per repo would allow this feature mentioned in #138 too.

a command line switch (maybe something like --strict-error-handling or something) should be added to allows users to choose to exit on errors if they want while defaulting to gracefully handling errors, logging what failed, and continuing.

If there is a failure on one repo, save state and move to next one. On next run each is able to recover or continue as needed.