From b089278c2b97c6292cc165015b484ddeee17e457 Mon Sep 17 00:00:00 2001 From: uhyo Date: Wed, 4 Jan 2023 13:18:59 +0900 Subject: [PATCH 1/4] Replace link to deprecated doc with latest link --- .../codespaces-reference/security-in-github-codespaces.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/codespaces/codespaces-reference/security-in-github-codespaces.md b/content/codespaces/codespaces-reference/security-in-github-codespaces.md index c27003a29f..d0ea1a942b 100644 --- a/content/codespaces/codespaces-reference/security-in-github-codespaces.md +++ b/content/codespaces/codespaces-reference/security-in-github-codespaces.md @@ -44,7 +44,7 @@ The token's scope will vary depending on the access you have to the repository w - **If you have write access to the repository**: The token will be scoped for read/write access to the repository. - **If you only have read access to the repository**: The token will only allow the code to be cloned from the source repository. If you attempt to push to a private repo where you only have read access, {% data variables.product.prodname_github_codespaces %} will prompt you to create a personal fork of the repository. The token will then be updated to have read/write access to the new personal fork. -- **If you've enabled your codespace to access other repositories**: When a codespace has been granted [access to other repositories](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces), any codespace created from that repository will have read/write tokens scoped to the source repository. In addition, the tokens will also receive read access to other repositories indicated by the user or organization. +- **If you've enabled your codespace to access other repositories**: When a codespace has been granted [access to other repositories](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces), any codespace created from that repository will have read/write tokens scoped to the source repository. In addition, the tokens will also receive read access to other repositories indicated by the user or organization. An organization's administrators specify which repositories should be considered trusted. An admin can [choose to trust](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces) none, all, or some of the organization's repositories. A codespace can't have greater permissions to access resources than the person who created it, even if the organization administrator has granted access to all users and all repositories. From 73efdf625316a2b1d0b0c95ec9d50bedec2a0749 Mon Sep 17 00:00:00 2001 From: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com> Date: Thu, 5 Jan 2023 09:12:55 +0000 Subject: [PATCH 2/4] Update content/codespaces/codespaces-reference/security-in-github-codespaces.md --- .../codespaces-reference/security-in-github-codespaces.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/codespaces/codespaces-reference/security-in-github-codespaces.md b/content/codespaces/codespaces-reference/security-in-github-codespaces.md index d0ea1a942b..b7706c29a5 100644 --- a/content/codespaces/codespaces-reference/security-in-github-codespaces.md +++ b/content/codespaces/codespaces-reference/security-in-github-codespaces.md @@ -44,7 +44,7 @@ The token's scope will vary depending on the access you have to the repository w - **If you have write access to the repository**: The token will be scoped for read/write access to the repository. - **If you only have read access to the repository**: The token will only allow the code to be cloned from the source repository. If you attempt to push to a private repo where you only have read access, {% data variables.product.prodname_github_codespaces %} will prompt you to create a personal fork of the repository. The token will then be updated to have read/write access to the new personal fork. -- **If you've enabled your codespace to access other repositories**: When a codespace has been granted [access to other repositories](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces), any codespace created from that repository will have read/write tokens scoped to the source repository. In addition, the tokens will also receive read access to other repositories indicated by the user or organization. +- **If you've authorized your codespace to access other repositories**: The token will be scoped for read or read/write access to the source repository and to any other repositories to which you've authorized access. For more information, see "[Managing access to other repositories within your codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces#authorizing-requested-permissions)." An organization's administrators specify which repositories should be considered trusted. An admin can [choose to trust](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces) none, all, or some of the organization's repositories. A codespace can't have greater permissions to access resources than the person who created it, even if the organization administrator has granted access to all users and all repositories. From c599be5ed33e62be9a6059b1de15eaac6791c7c1 Mon Sep 17 00:00:00 2001 From: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com> Date: Thu, 5 Jan 2023 09:13:27 +0000 Subject: [PATCH 3/4] Update content/codespaces/codespaces-reference/security-in-github-codespaces.md --- .../codespaces-reference/security-in-github-codespaces.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/codespaces/codespaces-reference/security-in-github-codespaces.md b/content/codespaces/codespaces-reference/security-in-github-codespaces.md index b7706c29a5..536d8f005f 100644 --- a/content/codespaces/codespaces-reference/security-in-github-codespaces.md +++ b/content/codespaces/codespaces-reference/security-in-github-codespaces.md @@ -46,7 +46,6 @@ The token's scope will vary depending on the access you have to the repository w - **If you only have read access to the repository**: The token will only allow the code to be cloned from the source repository. If you attempt to push to a private repo where you only have read access, {% data variables.product.prodname_github_codespaces %} will prompt you to create a personal fork of the repository. The token will then be updated to have read/write access to the new personal fork. - **If you've authorized your codespace to access other repositories**: The token will be scoped for read or read/write access to the source repository and to any other repositories to which you've authorized access. For more information, see "[Managing access to other repositories within your codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces#authorizing-requested-permissions)." -An organization's administrators specify which repositories should be considered trusted. An admin can [choose to trust](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces) none, all, or some of the organization's repositories. A codespace can't have greater permissions to access resources than the person who created it, even if the organization administrator has granted access to all users and all repositories. ### Codespace connections From 1d104c1785447a80f6e475d1c8dd4d5b85b7a674 Mon Sep 17 00:00:00 2001 From: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com> Date: Thu, 5 Jan 2023 09:19:29 +0000 Subject: [PATCH 4/4] Update content/codespaces/codespaces-reference/security-in-github-codespaces.md --- .../codespaces-reference/security-in-github-codespaces.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/codespaces/codespaces-reference/security-in-github-codespaces.md b/content/codespaces/codespaces-reference/security-in-github-codespaces.md index 23d04fa92c..16cc46ba3f 100644 --- a/content/codespaces/codespaces-reference/security-in-github-codespaces.md +++ b/content/codespaces/codespaces-reference/security-in-github-codespaces.md @@ -60,7 +60,7 @@ Organization owners can restrict the ability to make forward ports available pub **Privately forwarded ports**: Are accessible on the internet, but only the codespace creator can access them, after authenticating to {% data variables.product.product_name %}. -**Publicly forwarded portshin you witr organization**: Are accessible on the internet, but only to members of the same organization as the codespace, after authenticating to {% data variables.product.product_name %}. +**Publicly forwarded ports within your organization**: Are accessible on the internet, but only to members of the same organization as the codespace, after authenticating to {% data variables.product.product_name %}. **Publicly forwarded ports**: Are accessible on the internet, and anyone on the internet can access them. No authentication is needed to access public forwarded ports.