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

Add a note about gitconfig username and email automatic update #2692

Merged
merged 7 commits into from
Mar 25, 2024

Conversation

vinokurig
Copy link
Contributor

What does this pull request change?

Add a note about gitconfig username and email automatic update:
screenshot-0 0 0 0_4000-2024 02 22-14_42_58

What issues does this pull request fix or reference?

fixes eclipse-che/che#22828

Specify the version of the product this pull request applies to

Pull Request checklist

The author and the reviewers validate the content of this pull request with the following checklist, in addition to the automated tests.

  • Any procedure:
    • Successfully tested.
  • Any page or link rename:
    • The page contains a redirection for the previous URL.
    • Propagate the URL change in:
  • Builds on Eclipse Che hosted by Red Hat.
  • the Validate language on files added or modified step reports no vale warnings.

@vinokurig vinokurig requested review from deerskindoll and a team as code owners February 22, 2024 12:45
@vinokurig vinokurig requested a review from nickboldt February 22, 2024 12:45
Copy link

github-actions bot commented Feb 22, 2024

Click here to review and test in web IDE: Contribute

Copy link

github-actions bot commented Feb 22, 2024

🎊 Navigate the preview: https://65ef0b67beb394509caf613d--eclipse-che-docs-pr.netlify.app 🎊

@@ -46,6 +46,11 @@ __<ConfigMap_prepared_in_step_1>__
EOF
----

[NOTE]
====
The `user.name` and `user.email` fields can be set automatically from a git provider, connected to {prod-short} by a xref:using-a-git-provider-access-token.adoc[Git-provider access token]. The related data must be set in the provider's user profile page.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it supported for all providers?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is not only about access token, but also Git OAuth

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is not related directly to Git OAuth, the idea is to have a token secret either generated by Git OAuth, or manually created PAT secret. So the token documentation reference covers both cases.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

well, but it is linked with https://eclipse.dev/che/docs/stable/end-user-guide/using-a-git-provider-access-token/ that talks about PAT which is misleading

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mentioned the OAuth source as well.

@@ -46,6 +46,11 @@ __<ConfigMap_prepared_in_step_1>__
EOF
----

[NOTE]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's put the note at the top of the procedure, before pre-requirements

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've changed the configmap block to not to specify just username and email but generalise the gitconfig content:

screenshot-0 0 0 0_4000-2024 02 22-16_31_27

With this change I think the note suits here more as it specifies that the general gitconfig content can be updated automatically.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vinokurig this NOTE should be placed at the very beginning, just after the title Mounting Git configuration

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ibuziuk done

Copy link
Contributor

@deerskindoll deerskindoll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@ibuziuk
Copy link
Member

ibuziuk commented Mar 25, 2024

@deerskindoll we are good to merge

@vinokurig vinokurig merged commit defaca6 into main Mar 25, 2024
9 of 10 checks passed
@vinokurig vinokurig deleted the che-22828 branch March 25, 2024 10:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Gitconfig is not automatically created
4 participants