Skip to content

Commit

Permalink
additional fixes
Browse files Browse the repository at this point in the history
  • Loading branch information
@deerskindoll
deerskindoll committed Feb 6, 2024
1 parent 7523334 commit 00a846a
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions modules/end-user-guide/pages/using-a-git-provider-access-token.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,16 +9,14 @@

pass:[<!-- vale RedHat.Spelling = NO -->]

OAuth for GitHub, GitLab, Bitbucket, or Microsoft Azure Repos needs to be xref:administration-guide:configuring-oauth-for-git-providers.adoc[configured by the administrator] of your organization's {prod-short} instance. If your administrator could not configure it for {prod-short} users, the workaround is for you to use a personal access token. You can configure personal access tokens on the *User Preferences* page of your {prod-short} dashboard: `pass:c,a,q[{prod-url}]/dashboard/#/user-preferences?tab=personal-access-tokens`, or apply it manually as a {kubernetes} Secret in the namespace.
pass:[<!-- vale RedHat.CaseSensitiveTerms = NO -->]

pass:[<!-- vale RedHat.Spelling = YES -->]
OAuth for GitHub, GitLab, Bitbucket, or Microsoft Azure Repos needs to be xref:administration-guide:configuring-oauth-for-git-providers.adoc[configured by the administrator] of your organization's {prod-short} instance. If your administrator could not configure it for {prod-short} users, the workaround is for you to use a personal access token. You can configure personal access tokens on the *User Preferences* page of your {prod-short} dashboard: `pass:c,a,q[{prod-url}]/dashboard/#/user-preferences?tab=personal-access-tokens`, or apply it manually as a {kubernetes} Secret in the namespace.

Check failure on line 14 in modules/end-user-guide/pages/using-a-git-provider-access-token.adoc

View workflow job for this annotation

GitHub Actions / Linting with Vale 

[vale] reported by reviewdog 🐶
[RedHat.CaseSensitiveTerms] Use 'Git' rather than 'git'.

Raw Output:
{"message": "[RedHat.CaseSensitiveTerms] Use 'Git' rather than 'git'.", "location": {"path": "modules/end-user-guide/pages/using-a-git-provider-access-token.adoc", "range": {"start": {"line": 14, "column": 123}}}, "severity": "ERROR"}

Mounting your access token as a Secret enables the {prod-short} Server to access the remote repository that is cloned during workspace creation, including access to the repository's `/.che` and `/.vscode` folders.

Apply the Secret in your user {orch-namespace} of the {orch-name} cluster of your organization's {prod-short} instance.

pass:[<!-- vale RedHat.Spelling = NO -->]

After applying the Secret, you can create workspaces with clones of private Git repositories that are hosted on GitHub, GitLab, Bitbucket Server, or Microsoft Azure Repos.

pass:[<!-- vale RedHat.Spelling = YES -->]
Expand Down Expand Up @@ -132,3 +130,5 @@ EOF

* xref:administration-guide:deploying-che-with-support-for-git-repositories-with-self-signed-certificates.adoc[Deploying Che with support for Git repositories with self-signed certificates]
* link:https://docs.github.com/en/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on[Authorizing a personal access token for use with SAML single sign-on]

pass:[<!-- vale RedHat.CaseSensitiveTerms = YES -->]

0 comments on commit 00a846a

Please sign in to comment.