-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Provision name and email from user profile if preferences are empty #14508
Conversation
ci-build |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't particularly like the lambda nesting. I think it could be made more clear using the approach I'm showing in the comment...
...org/eclipse/che/workspace/infrastructure/kubernetes/provision/GitUserProfileProvisioner.java
Outdated
Show resolved
Hide resolved
E2E tests of Eclipse Che Multiuser on OCP has been successful:
|
...org/eclipse/che/workspace/infrastructure/kubernetes/provision/GitUserProfileProvisioner.java
Outdated
Show resolved
Hide resolved
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has been successful:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reapproving new changes
Signed-off-by: Vlad Zhukovskyi <vzhukovs@redhat.com>
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
What does this PR do?
This changes proposal adds a behavior when user name and user email from user profile is taken to provision default git configuration, when user preferences are empty. But, when user preferences are contain information about user name and email, then user name and email from user profile is ignored.
Signed-off-by: Vlad Zhukovskyi vzhukovs@redhat.com
What issues does this PR fix or reference?
#14416
Release Notes
Provision name and email from user profile if preferences are empty
Docs PR
N/A