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

username provide to the git commiter should be first name + lastname #15419

Open
sunix opened this issue Dec 6, 2019 · 3 comments
Open

username provide to the git commiter should be first name + lastname #15419

sunix opened this issue Dec 6, 2019 · 3 comments
Labels
area/dogfooding Using Eclispe Che to code, test and build Eclipse Che area/git/dev-environment-config Issues and PRs related to the automatic setup of git within a cloud development environment area/git/oauth-services OAuth support to authenticate developers with their GitHub, GitLab, Bitbucket etc...accounts good first issue Community, this issue looks easy to start with for a new contributor. Just take it. We'll help you! kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@sunix
Copy link
Contributor

sunix commented Dec 6, 2019

Describe the bug

#14416 provides a nice feature: the Che user don't have to fill his name and email to perform a git commit: all is already injected with the default information that the user have generally provided when creating its user profile.
The problem is, name use is the username, not the first name + the last name. Which is not very nice when username is not meaning full. For instance, in some environment, my username is user1.

when executing git log:

commit 8e804b49c7313a036d4c973f4718b618dad6b5d8
Author: user1 <sutan@redhat.com>
Date:   Thu Dec 5 15:24:50 2019 +0000

    removing unused yarn.lock that also contain security warning

commit 4ed171b13f05df5417ec9995ff0295ff1145633f
Author: user1 <sutan@redhat.com>
Date:   Thu Dec 5 15:08:43 2019 +0000

    adding missing env file (was in .gitignore ...)

commit afba9a437aac4cc83fc72508abd70ef9a9c44bd0
Author: user1 <sutan@redhat.com>
Date:   Thu Dec 5 14:57:05 2019 +0000

    Reenable react devmode by using proxy feature
@sunix sunix added kind/bug Outline of a bug - must adhere to the bug report template. team/ide area/editor/theia Issues related to the che-theia IDE of Che labels Dec 6, 2019
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Dec 6, 2019
@tolusha tolusha added severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Dec 8, 2019
@sunix sunix added good first issue Community, this issue looks easy to start with for a new contributor. Just take it. We'll help you! area/git labels Mar 29, 2020
@benoitf benoitf added dogfooding area/che-server and removed area/editor/theia Issues related to the che-theia IDE of Che labels Jul 30, 2020
@che-bot
Copy link
Contributor

che-bot commented Feb 4, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 4, 2021
@ericwill ericwill added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 4, 2021
@l0rd l0rd added area/git/dev-environment-config Issues and PRs related to the automatic setup of git within a cloud development environment area/git/oauth-services OAuth support to authenticate developers with their GitHub, GitLab, Bitbucket etc...accounts and removed area/git labels Jan 23, 2023
@d4nnyp73
Copy link

d4nnyp73 commented Jun 4, 2023

Hey i want to start contributing and would take this as my first issue, if i can ! :)

i would be verry happy if you could assign this issue to me !

Cheers

@dmytro-ndp dmytro-ndp added area/dogfooding Using Eclispe Che to code, test and build Eclipse Che and removed dogfooding labels Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dogfooding Using Eclispe Che to code, test and build Eclipse Che area/git/dev-environment-config Issues and PRs related to the automatic setup of git within a cloud development environment area/git/oauth-services OAuth support to authenticate developers with their GitHub, GitLab, Bitbucket etc...accounts good first issue Community, this issue looks easy to start with for a new contributor. Just take it. We'll help you! kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

10 participants