feat: Add note about CHE_FORCE_REFRESH_PERSONAL_ACCESS_TOKEN feature (#…

…2749)

* feat: Add note about CHE_FORCE_REFRESH_PERSONAL_ACCESS_TOKEN feature

Signed-off-by: Anatolii Bazko <abazko@redhat.com>

* Fixup

Signed-off-by: Anatolii Bazko <abazko@redhat.com>

---------

Signed-off-by: Anatolii Bazko <abazko@redhat.com>

modules/administration-guide/pages/configuring-oauth-for-git-providers.adoc

@@ -7,10 +7,25 @@
 [id="configuring-oauth-for-git-providers"]
 = Configuring OAuth for Git providers
 
+[NOTE]
+====
+To enable the experimental feature that forces a refresh of the personal access token on workspace startup in {prod}, modify the Custom Resource configuration as follows:
+
+[source,yaml]
+----
+spec:
+  components:
+    cheServer:
+      extraProperties:
+        CHE_FORCE_REFRESH_PERSONAL_ACCESS_TOKEN: "true"
+----
+====
+
 You can configure OAuth between {prod-short} and Git providers, enabling users to work with remote Git repositories:
 
 * xref:configuring-oauth-2-for-github.adoc[]
 * xref:configuring-oauth-2-for-gitlab.adoc[]
 * Configuring xref:configuring-oauth-2-for-a-bitbucket-server.adoc[OAuth 2.0 for a Bitbucket Server] or xref:configuring-oauth-2-for-the-bitbucket-cloud.adoc[OAuth 2.0 for the Bitbucket Cloud]
 * Configuring xref:configuring-oauth-1-for-a-bitbucket-server.adoc[OAuth 1.0 for a Bitbucket Server]
 * xref:configuring-oauth-2-for-microsoft-azure-devops-services.adoc[]
+