-
Notifications
You must be signed in to change notification settings - Fork 438
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
Enhancement: use local git user for stub runner by default #1206
Comments
I'm sorry but can you create the issue properly from the beginning until the end? I have no idea what the problem is, for which version, what you did and what you're planning to do. |
updated |
What did you update? This issue? Can you please read the comment we're providing for better issue creation when you click on the
Also please read on how to ask a good question on SO (it can give you pointers to how ask good questions on GitHub too) - https://stackoverflow.com/help/how-to-ask |
I meant that I'd edited the description, i.e. the first comment. I don't really know what to add, don't have time to set up a whole project but basically, when using any stub runner and specifying The suggestion is to use local Git user credentials by default. Here is my reasoning: Hopefully, that's clear enough. |
Found #1205 and your response actually solves my problem! If I execute these 2 lines then I don't need to provide username and password, which is exactly what my concern was. #1205 (comment) I suggest updating the documentation. Otherwise, the issue may be closed |
Great, are you willing to do a PR? :) That would be a nice contribution (over here I guess https://github.com/spring-cloud/spring-cloud-contract/blob/master/docs/src/main/asciidoc/howto.adoc#how-can-i-use-git-as-the-storage-for-contracts-and-stubs) |
I want to run my stubs that are stored in Git without having to provide git username and password. The stub runner must be able to just use my local git account, that I am using with Git CLI.
version 2.1.2.RELEASE, maven runner
The text was updated successfully, but these errors were encountered: