This is an automated email from the ASF dual-hosted git repository. lynwee pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/incubator-devlake-website.git
commit cbfc6d2e0e5c0bdd087420aab4593759d3895236 Author: Lynwee <[email protected]> AuthorDate: Thu Sep 21 11:00:28 2023 +0800 docs(trouble shooting): revise it with Google Bard --- docs/Troubleshooting/Configuration.md | 9 ++++----- versioned_docs/version-v0.19/Troubleshooting/Configuration.md | 8 ++++---- 2 files changed, 8 insertions(+), 9 deletions(-) diff --git a/docs/Troubleshooting/Configuration.md b/docs/Troubleshooting/Configuration.md index 4ae97da931..972b02707c 100644 --- a/docs/Troubleshooting/Configuration.md +++ b/docs/Troubleshooting/Configuration.md @@ -68,14 +68,13 @@ Here is an example of the `docker-compose` installation, the idea applies to oth command: --innodb-buffer-pool-size=200M ``` -### Repositories don't show up to select for data scopes in GitHub connections -See issue [#6038](https://github.com/apache/incubator-devlake/issues/6038) - -First you should check whether you access token has necessary permissions, if permissions are correct. Please make sure that after creating the token you have authorized it using SSO if your account are protected by organization SAML enforcement. +### Repositories don't show up for selection as data scopes in GitHub connections -More details about authenticating with SAML single sign-on can be seen [here](https://docs.github.com/en/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on). +See issue [#6038](https://github.com/apache/incubator-devlake/issues/6038) +First, check if your access token has the necessary permissions. If the permissions are correct, make sure that you have authorized the token using SSO if your account is protected by organization SAML enforcement. +For more details about authenticating with SAML single sign-on, see here: https://docs.github.com/en/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on. ## None of them solve your problem? diff --git a/versioned_docs/version-v0.19/Troubleshooting/Configuration.md b/versioned_docs/version-v0.19/Troubleshooting/Configuration.md index 4ae97da931..6736e0fd6f 100644 --- a/versioned_docs/version-v0.19/Troubleshooting/Configuration.md +++ b/versioned_docs/version-v0.19/Troubleshooting/Configuration.md @@ -68,13 +68,13 @@ Here is an example of the `docker-compose` installation, the idea applies to oth command: --innodb-buffer-pool-size=200M ``` -### Repositories don't show up to select for data scopes in GitHub connections -See issue [#6038](https://github.com/apache/incubator-devlake/issues/6038) +### Repositories don't show up for selection as data scopes in GitHub connections -First you should check whether you access token has necessary permissions, if permissions are correct. Please make sure that after creating the token you have authorized it using SSO if your account are protected by organization SAML enforcement. +See issue [#6038](https://github.com/apache/incubator-devlake/issues/6038) -More details about authenticating with SAML single sign-on can be seen [here](https://docs.github.com/en/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on). +First, check if your access token has the necessary permissions. If the permissions are correct, make sure that you have authorized the token using SSO if your account is protected by organization SAML enforcement. +For more details about authenticating with SAML single sign-on, see here: https://docs.github.com/en/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on. ## None of them solve your problem?
