Skip to content

Commit

Permalink
Update website/docs/faqs/Troubleshooting/error-importing-repo.md
Browse files Browse the repository at this point in the history
Co-authored-by: nataliefiann <[email protected]>
  • Loading branch information
mirnawong1 and nataliefiann authored Dec 10, 2024
1 parent 0154a1a commit 93ed866
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion website/docs/faqs/Troubleshooting/error-importing-repo.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,4 +11,4 @@ If you don't see your repository listed, double-check that:
If you do see your repository listed, but are unable to import the repository successfully, double-check that:
- You are a maintainer of that repository. Only users with maintainer permissions can set up repository connections.

If you imported a repository using the dbt Cloud native integration with GitLab, you should be able to see the clone strategy is using a `deploy_token`. If it's relying on an SSH key, this means the repository was not set up using the native GitLab integration, but rather using the generic git clone option. The repository must be reconnected in order to get the benefits described above.
If you imported a repository using the dbt Cloud native integration with GitLab, you should be able to see if the clone strategy is using a `deploy_token`. If it's relying on an SSH key, this means the repository was not set up using the native GitLab integration, but rather using the generic git clone option. The repository must be reconnected in order to get the benefits described above.

0 comments on commit 93ed866

Please sign in to comment.