Skip to content
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

[feature request] flag to skip repos require auth #15

Open
a-b opened this issue May 30, 2015 · 5 comments
Open

[feature request] flag to skip repos require auth #15

a-b opened this issue May 30, 2015 · 5 comments

Comments

@a-b
Copy link

a-b commented May 30, 2015

Hello and thanks for such a great product!

For users who has a lot of old repos it would be really handy to have a flag to skip broken repos or repos with outdated auth.
Thanks!

@earwig
Copy link
Owner

earwig commented May 31, 2015

Not sure how that would work. What sort of broken repos could it detect? I'm not sure what outdated auth means in this case.

Or are you just looking for a way to specify exclusion patterns? That sounds doable.

@a-b
Copy link
Author

a-b commented Jun 7, 2015

I think I can do exclusion patterns using regular unix tools or zsh wildcard extensions.
I'm trying to cover situation when one of the repos in the directory has some problems or errors and git return error:

web:                                                                                              │
        Error: no remotes configured to pull from.

In this case I want to have a flag which will gracefully skip this repo and continue to update other git repos.

@earwig
Copy link
Owner

earwig commented Jun 8, 2015

I don't understand. gitup doesn't stop updating just because one repo has an error. Can you check again?

Edit: Never mind, I get it.

@romeojulietthotel
Copy link

romeojulietthotel commented Jul 2, 2018

This is really a bug, right?

The problem can occur in two ways (at least on github):

  • A previously public repo is now private
  • A previous repo has been deleted

Both cases cause github to ask for a username/password as part of github authentication. They don't want to leak information about private repos.

I hit enter twice to get past this but that means that gitup can no longer be run from cron with the expectation of having all local repos get updated. It now requires human interaction because it blocks on wating for the username/password or htting enter twice.

I looked for some way using native git to get around this problem but couldn't find a way.

@earwig
Copy link
Owner

earwig commented Jul 2, 2018

That seems fair. I'll see what I can do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants