-
Notifications
You must be signed in to change notification settings - Fork 2
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
Document how to pass the necessary credentials to allow push to remote GIT repository #33
Comments
Wow! Not sure how we missed that. If you aren't using SSH: Lines 177 to 196 in 8884a8b
If you are using SSH: Lines 177 to 196 in 8884a8b
Agreed we should document better. |
Thanks for your answer. In the mean time I figure out the issue on my side. The problem was when integrating it in gitlab ci. I had to change the branch which was cloned and the remote origin to use another user than the ci user. This was not that easy to figure out that one, don’t how I could avoid this for the next one who wants to do that. |
How about if git errors looked like this:
Anything missing from the above which would have helped resolve your case? |
Seems good to me! |
Currently it is not clear how we should pass credentials (or what is the strategy) to configure push to remote git repository, could you please update documentation to clarify that point?
The text was updated successfully, but these errors were encountered: