Skip to content
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

Merged
merged 1 commit into from
Sep 12, 2019

Conversation

vzhukovs
Copy link
Contributor

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

@vzhukovs vzhukovs added kind/enhancement A feature request - must adhere to the feature request template. team/ide severity/P1 Has a major impact to usage or development of the system. labels Sep 11, 2019
@vzhukovs vzhukovs added this to the 7.2.0 milestone Sep 11, 2019
@vzhukovs vzhukovs self-assigned this Sep 11, 2019
@che-bot che-bot added the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Sep 11, 2019
@vzhukovs
Copy link
Contributor Author

ci-build

@che-bot
Copy link
Contributor

che-bot commented Sep 11, 2019

E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:

  • build details
  • "che-server" docker image: maxura/che-server:14508

@che-bot
Copy link
Contributor

che-bot commented Sep 11, 2019

E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:

  • build details
  • "che-server" docker image: maxura/che-server:14508

Copy link
Contributor

@metlos metlos left a 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...

@che-bot
Copy link
Contributor

che-bot commented Sep 11, 2019

E2E tests of Eclipse Che Multiuser on OCP has been successful:

@che-bot
Copy link
Contributor

che-bot commented Sep 11, 2019

E2E tests of Eclipse Che Multiuser on OCP has failed:

@che-bot
Copy link
Contributor

che-bot commented Sep 11, 2019

E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:

  • build details
  • "che-server" docker image: maxura/che-server:14508

@che-bot
Copy link
Contributor

che-bot commented Sep 11, 2019

E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:

  • build details
  • "che-server" docker image: maxura/che-server:14508

@che-bot
Copy link
Contributor

che-bot commented Sep 11, 2019

E2E tests of Eclipse Che Multiuser on OCP has been successful:

Copy link
Contributor

@amisevsk amisevsk left a 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>
@che-bot
Copy link
Contributor

che-bot commented Sep 12, 2019

E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:

  • build details
  • "che-server" docker image: maxura/che-server:14508

@che-bot
Copy link
Contributor

che-bot commented Sep 12, 2019

E2E tests of Eclipse Che Multiuser on OCP has failed:

@vzhukovs vzhukovs merged commit ac7a404 into master Sep 12, 2019
@vzhukovs vzhukovs deleted the che#14416 branch September 12, 2019 11:55
@che-bot che-bot removed the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Sep 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants