Passwords for private repos?

[097115]

Now it says:

Command failed: exit status 1
fatal: could not read Password for 'my-private-repo': terminal prompts disabled

Would be greta to have some workaround may be... Otherwise very handy indeed 👍

[robin-mbg]

Hello 097115, good to hear that may comes in handy 😀 I'm not sure yet how best to handle git repositories that interactively require input.

Updating private repositories only works

• if the repository was checked out via SSH ( StackOverflow)
• if some component, e.g. the git-credential-store, makes sure that the password does not need to be provided interactively (StackOverflow)

In my experience, this does cover the most common use cases, but it would be great to get another view on this topic. Maybe it does make sense to include something like an -i flag in the future that moves git's interactive requests for input to the foreground.

[097115]

@robin-mbg , thanks for your comment!

I agree that may does cover the most common use cases, and that private repos mostly aren't those that are usually updated in bulk :)

However, your suggestion to add this additional parameter to move interactive requests to the foreground sounds rational and doesn't seem to complicate the existing routine. Would be great to see that implemented sometime in the future :)

Thanks again for your support.

[robin-mbg]

Just so we don't misunderstand each other: Bulk-updating private repositories is absolutely within the feature-set of may. Checking out private repositories via SSH is the most secure method of dealing with pivate repositories and repositories that have been cloned in this way are easily bulk-updated using may. With locally cached or stored credentials, repositories checked out via HTTPS are also supported. The issue only arises when checking out via HTTPS AND not storing credentials locally.

Adding an additional flag for interactive input could absolutely be an addition for a future release, but I would nonetheless recommend that you check out your private repositories using SSH. I know this might not be possible (older versions of Gitlab for example don't support this yet), but should be done whenever possible.