jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-25 02:17:36 -05:00
Code Issues Projects Releases Wiki Activity

Correct internal links to codespaces/reference/ (#44921)

Browse Source
This commit is contained in:
Peter Bengtsson
2023-10-24 07:33:45 -04:00
committed by GitHub
parent 44902069ae
commit 7c5dfd787b
51 changed files with 116 additions and 116 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/codespaces/troubleshooting/troubleshooting-authentication-to-a-repository.md
View File

@@ -1,6 +1,6 @@
---
title: Troubleshooting authentication to a repository
intro: Learn how to troubleshoot common authentication issues when you clone, push to, or pull from a repository in a codespace.
intro: 'Learn how to troubleshoot common authentication issues when you clone, push to, or pull from a repository in a codespace.'
versions:
fpt: '*'
ghec: '*'
@@ -43,7 +43,7 @@ The `GITHUB_TOKEN` in a codespace is configured with read and write access to th
We do not recommend manually updating the value of the `GITHUB_TOKEN` in a codespace. If your project requires access to other repositories, you can give codespaces access to these repositories by listing additional permissions in your dev container configuration. This will allow users to authorize the additional permissions when they create a codespace. However, it will not change the permissions of an existing codespace. For more information, see "[AUTOTITLE](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)."
If you need access to another repository in an existing codespace, or if the permissions you need are specific to you and don't apply to other contributors, you can create a {% data variables.product.pat_generic %} with access to the repository and add the token to your codespace. We recommend you limit the token's access by using a {% data variables.product.pat_v2 %}, selecting only the repositories to which you need access, and giving the required access to the **Contents** permission only. For more information, see "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token#creating-a-fine-grained-personal-access-token)."
If you need access to another repository in an existing codespace, or if the permissions you need are specific to you and don't apply to other contributors, you can create a {% data variables.product.pat_generic %} with access to the repository and add the token to your codespace. We recommend you limit the token's access by using a {% data variables.product.pat_v2 %}, selecting only the repositories to which you need access, and giving the required access to the **Contents** permission only. For more information, see "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-fine-grained-personal-access-token)."
You can then add the token as an environment variable in a codespace, or as a secret for {% data variables.product.prodname_github_codespaces %}. If you create a secret, you should only allow certain trusted repositories to access the secret. When you add a new secret, you will be prompted to reload your existing codespace to pull in the new secret. For more information, see "[AUTOTITLE](/codespaces/managing-your-codespaces/managing-secrets-for-your-codespaces)."