You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Backup of private organization does nothing, no errors #72
github-backup <NAME> --private --organization --output-directory ~/gitbak --all
Retrieving repositories
Filtering repositories
Backing up repositories
Retrieving <NAME> starred repositories
Writing 0 starred repositories to disk
Retrieving <NAME> watched repositories
Writing 0 watched repositories to disk
$ tree ~/gitbak/
/home/user/gitbak/
└── account
├── starred.json
└── watched.json
1 directory, 2 files
I would also be nice to have a --debug option for additional output of what is going on. I can clone our repos via ssh just fine. leaving out the ssh option did not make a difference.
I started adding some logging info to debug this, turns out the request returns back an empty list, []. Turns out -u is required, but not checked for. Which then prompts for a password, which it should not if I issued to prefer ssh
bin/github-backup -u user <NAME>--prefer-ssh --private --organization --output-directory ~/gitbak --all
Backing up user <NAME> to /home/user/gitbak
Retrieving repositories
Password:
If -u is left out, getpasswd should be used to obtain the current user.
@mtdeguzis If you set --user, you probably also want to set --password (its for basic auth). The alternative is to use a token, as you found. getpasswd isnt a good alternative here because your local username probably does not match your github username (mine doesn't).
I suppose if we set the --private flag, we should also check for auth. Mind making a pull request for that?
We actually need to check for user. If that is left out, the program kicks of as if nothing is wrong. But I get what you mean, get_auth can be issued if --private is used.
Activity
asdf1234-deleted commentedon Nov 27, 2017
I started adding some logging info to debug this, turns out the request returns back an empty list, []. Turns out -u is required, but not checked for. Which then prompts for a password, which it should not if I issued to prefer ssh
If -u is left out, getpasswd should be used to obtain the current user.
asdf1234-deleted commentedon Nov 27, 2017
Ok works with a token, all of which these things should be checked for at runtime. Is there no other way?
josegonzalez commentedon Nov 27, 2017
@mtdeguzis If you set
--user, you probably also want to set--password(its for basic auth). The alternative is to use a token, as you found.getpasswdisnt a good alternative here because your local username probably does not match your github username (mine doesn't).I suppose if we set the
--privateflag, we should also check for auth. Mind making a pull request for that?asdf1234-deleted commentedon Nov 28, 2017
I could probably take a look at add the check. I'll look at submitting a PR.
asdf1234-deleted commentedon Nov 28, 2017
Actually, this checks for the pw, so nothing to do here:
We actually need to check for user. If that is left out, the program kicks of as if nothing is wrong. But I get what you mean, get_auth can be issued if --private is used.
asdf1234-deleted commentedon Nov 28, 2017
How about..
... when a user attempts to retrieve data from a private repository?
breezzz commentedon Feb 12, 2018
Hello! It would be nice to add authentication by the ssh key (without password)
josegonzalez commentedon Feb 12, 2018
@breezzz pull request welcome.
whwright commentedon Dec 27, 2018
This looks done with #74?
josegonzalez commentedon Dec 27, 2018
That was never merged.
whwright commentedon Dec 27, 2018
Derp, somehow missed that. Should this be implemented as a failure or a warning? I am thinking similar to this:
python-github-backup/bin/github-backup
Line 539 in 89ee22c
josegonzalez commentedon Dec 28, 2018
warning is fine.
Iamrodos commentedon Dec 7, 2025
@josegonzalez this can be closed. Addressed by aba048a in PR #461