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
That mechanism is used for example when pushing to GitHub from CI server with security tokens.
There is a simple workaround - passing username/password in Credential object, but it could be hard to apply/not supported when GrGit is used through the 3rd tools. Therefore it would be good to support also credentials encoded in the URL.
The text was updated successfully, but these errors were encountered:
Since, I'm just passing the URLs straight into JGit, I think that's where the limitation is. Another way to work around this would be to use the system properties noted in the docs.
Git itself supports passing username or/and password in HTTPS connection URL, e.g.
That mechanism is used for example when pushing to GitHub from CI server with security tokens.
There is a simple workaround - passing username/password in Credential object, but it could be hard to apply/not supported when GrGit is used through the 3rd tools. Therefore it would be good to support also credentials encoded in the URL.
The text was updated successfully, but these errors were encountered: