From a80ebac6d9f96af0ba83650eff5c1a0554e7d77c Mon Sep 17 00:00:00 2001 From: Andre Kolodochka <59625655+andrekolodochka@users.noreply.github.com> Date: Wed, 25 Aug 2021 12:25:00 +1000 Subject: [PATCH 01/12] Update removing-a-member-from-your-organization.md --- .../removing-a-member-from-your-organization.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md index 5a6a4890a1..fb0e692b8d 100644 --- a/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md +++ b/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md @@ -33,6 +33,7 @@ Only organization owners can remove members from an organization. **Warning:** When you remove members from an organization: - Removed members will lose access to private forks of your organization's private repositories, but may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. + - For customers with [Enterprise Account](/articles/managing-your-enterprise-account/about-enterprise-accounts/), removed members will lose access to private forks of your organization's internal repositories, but only when the removed member is not a member of another organization under that Enterprise Account. - Any organization invitations sent by the removed user, that have not been accepted, are cancelled and will not be accessible. {% endwarning %} From 34ec30a4f1309848d38ae5c91400dc366f40aba5 Mon Sep 17 00:00:00 2001 From: Andre Kolodochka <59625655+andrekolodochka@users.noreply.github.com> Date: Wed, 25 Aug 2021 12:42:29 +1000 Subject: [PATCH 02/12] Update removing-a-member-from-your-organization.md --- .../removing-a-member-from-your-organization.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md index fb0e692b8d..8d1c7fd0d8 100644 --- a/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md +++ b/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md @@ -23,6 +23,7 @@ Only organization owners can remove members from an organization. **Warning:** When you remove members from an organization: - The paid license count does not automatically downgrade. To pay for fewer licenses after removing users from your organization, follow the steps in "[Downgrading your organization's paid seats](/articles/downgrading-your-organization-s-paid-seats)." - Removed members will lose access to private forks of your organization's private repositories, but they may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. +- For customers with [Enterprise Account](/articles/managing-your-enterprise-account/about-enterprise-accounts/), removed members will lose access to private forks of your organization's internal repositories, but only when the removed member is not a member of another organization under that Enterprise Account. - Any organization invitations sent by a removed member, that have not been accepted, are cancelled and will not be accessible. {% endwarning %} From b48d94650a0712d829cec1cf1d2d5f3c28599d62 Mon Sep 17 00:00:00 2001 From: Andre Kolodochka <59625655+andrekolodochka@users.noreply.github.com> Date: Wed, 25 Aug 2021 12:59:12 +1000 Subject: [PATCH 03/12] Update removing-a-member-from-your-organization.md --- .../removing-a-member-from-your-organization.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md index 8d1c7fd0d8..0101517c3b 100644 --- a/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md +++ b/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md @@ -23,7 +23,7 @@ Only organization owners can remove members from an organization. **Warning:** When you remove members from an organization: - The paid license count does not automatically downgrade. To pay for fewer licenses after removing users from your organization, follow the steps in "[Downgrading your organization's paid seats](/articles/downgrading-your-organization-s-paid-seats)." - Removed members will lose access to private forks of your organization's private repositories, but they may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. -- For customers with [Enterprise Account](/articles/managing-your-enterprise-account/about-enterprise-accounts/), removed members will lose access to private forks of your organization's internal repositories, but only when the removed member is not a member of another organization under that Enterprise Account. +- For customers with [Enterprise Account](https://docs.github.com/en/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts), removed members will lose access to private forks of your organization's internal repositories, but only when the removed member is not a member of another organization under that Enterprise Account. - Any organization invitations sent by a removed member, that have not been accepted, are cancelled and will not be accessible. {% endwarning %} @@ -34,7 +34,7 @@ Only organization owners can remove members from an organization. **Warning:** When you remove members from an organization: - Removed members will lose access to private forks of your organization's private repositories, but may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. - - For customers with [Enterprise Account](/articles/managing-your-enterprise-account/about-enterprise-accounts/), removed members will lose access to private forks of your organization's internal repositories, but only when the removed member is not a member of another organization under that Enterprise Account. + - For customers with [Enterprise Account](https://docs.github.com/en/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts), removed members will lose access to private forks of your organization's internal repositories, but only when the removed member is not a member of another organization under that Enterprise Account. - Any organization invitations sent by the removed user, that have not been accepted, are cancelled and will not be accessible. {% endwarning %} From 8a587d2a9c37ccc6d31199f37c25c5f7822d9856 Mon Sep 17 00:00:00 2001 From: Andre Kolodochka <59625655+andrekolodochka@users.noreply.github.com> Date: Wed, 25 Aug 2021 13:12:01 +1000 Subject: [PATCH 04/12] Update content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md Co-authored-by: Daniel Figucio <745341+affrae@users.noreply.github.com> --- .../removing-a-member-from-your-organization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md index 0101517c3b..55dfeb99ed 100644 --- a/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md +++ b/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md @@ -23,7 +23,7 @@ Only organization owners can remove members from an organization. **Warning:** When you remove members from an organization: - The paid license count does not automatically downgrade. To pay for fewer licenses after removing users from your organization, follow the steps in "[Downgrading your organization's paid seats](/articles/downgrading-your-organization-s-paid-seats)." - Removed members will lose access to private forks of your organization's private repositories, but they may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. -- For customers with [Enterprise Account](https://docs.github.com/en/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts), removed members will lose access to private forks of your organization's internal repositories, but only when the removed member is not a member of another organization under that Enterprise Account. +- In addition, for customers with [Enterprise Accounts](https://docs.github.com/en/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts), removed members will lose access to private forks of your organization's internal repositories in this manner when and only when the removed member is not a member of another organization under that Enterprise Account. - Any organization invitations sent by a removed member, that have not been accepted, are cancelled and will not be accessible. {% endwarning %} From 21463489eb1518d53db814bc277fb03839e6d01e Mon Sep 17 00:00:00 2001 From: Andre Kolodochka <59625655+andrekolodochka@users.noreply.github.com> Date: Wed, 25 Aug 2021 13:12:10 +1000 Subject: [PATCH 05/12] Update content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md Co-authored-by: Daniel Figucio <745341+affrae@users.noreply.github.com> --- .../removing-a-member-from-your-organization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md index 55dfeb99ed..8655272c0b 100644 --- a/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md +++ b/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md @@ -34,7 +34,7 @@ Only organization owners can remove members from an organization. **Warning:** When you remove members from an organization: - Removed members will lose access to private forks of your organization's private repositories, but may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. - - For customers with [Enterprise Account](https://docs.github.com/en/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts), removed members will lose access to private forks of your organization's internal repositories, but only when the removed member is not a member of another organization under that Enterprise Account. + - In addition, for customers with [Enterprise Accounts](https://docs.github.com/en/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts), removed members will lose access to private forks of your organization's internal repositories in this manner when and only when the removed member is not a member of another organization under that Enterprise Account. - Any organization invitations sent by the removed user, that have not been accepted, are cancelled and will not be accessible. {% endwarning %} From c558b34f7a365bddf67755ab4a3c586ebb0164e2 Mon Sep 17 00:00:00 2001 From: Nick Liffen Date: Mon, 30 Aug 2021 10:36:42 +0100 Subject: [PATCH 06/12] Update setting-up-code-scanning-for-a-repository.md --- .../setting-up-code-scanning-for-a-repository.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index 5d61fc58e1..cd4724fa18 100644 --- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -57,7 +57,8 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a In the default {% data variables.product.prodname_codeql_workflow %}, {% data variables.product.prodname_code_scanning %} is configured to analyze your code each time you either push a change to the default branch or any protected branches, or raise a pull request against the default branch. As a result, {% data variables.product.prodname_code_scanning %} will now commence. ## Bulk set up of {% data variables.product.prodname_code_scanning %} -You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. For an example of a script that raises pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository. + +You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. For an example of a script that raises pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using Powershell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have Powershell and instead would like to use NodeJS. ## Understanding the pull request checks From 2d0efc3a66d42ddcafb6d35f16082897dd9d7e13 Mon Sep 17 00:00:00 2001 From: Andre Kolodochka <59625655+andrekolodochka@users.noreply.github.com> Date: Fri, 10 Sep 2021 11:30:01 +1000 Subject: [PATCH 07/12] Adding double quotes to Ruby script --- .../building-github-apps/authenticating-with-github-apps.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/developers/apps/building-github-apps/authenticating-with-github-apps.md b/content/developers/apps/building-github-apps/authenticating-with-github-apps.md index 1958a66ea0..eec6ecdec4 100644 --- a/content/developers/apps/building-github-apps/authenticating-with-github-apps.md +++ b/content/developers/apps/building-github-apps/authenticating-with-github-apps.md @@ -72,7 +72,7 @@ require 'openssl' require 'jwt' # https://rubygems.org/gems/jwt # Private key contents -private_pem = File.read(YOUR_PATH_TO_PEM) +private_pem = File.read("YOUR_PATH_TO_PEM") private_key = OpenSSL::PKey::RSA.new(private_pem) # Generate the JWT @@ -82,7 +82,7 @@ payload = { # JWT expiration time (10 minute maximum) exp: Time.now.to_i + (10 * 60), # {% data variables.product.prodname_github_app %}'s identifier - iss: YOUR_APP_ID + iss: "YOUR_APP_ID" } jwt = JWT.encode(payload, private_key, "RS256") From 5caa90b033c80e6978635d01d9ff1c552801bf1b Mon Sep 17 00:00:00 2001 From: Andre Kolodochka <59625655+andrekolodochka@users.noreply.github.com> Date: Fri, 10 Sep 2021 11:37:40 +1000 Subject: [PATCH 08/12] Update authenticating-with-github-apps.md --- .../building-github-apps/authenticating-with-github-apps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/developers/apps/building-github-apps/authenticating-with-github-apps.md b/content/developers/apps/building-github-apps/authenticating-with-github-apps.md index eec6ecdec4..70a5269dbf 100644 --- a/content/developers/apps/building-github-apps/authenticating-with-github-apps.md +++ b/content/developers/apps/building-github-apps/authenticating-with-github-apps.md @@ -89,7 +89,7 @@ jwt = JWT.encode(payload, private_key, "RS256") puts jwt ``` -`YOUR_PATH_TO_PEM` and `YOUR_APP_ID` are the values you must replace. +`YOUR_PATH_TO_PEM` and `YOUR_APP_ID` are the values you must replace and make sure to enclose them in double quotes. Use your {% data variables.product.prodname_github_app %}'s identifier (`YOUR_APP_ID`) as the value for the JWT [iss](https://tools.ietf.org/html/rfc7519#section-4.1.1) (issuer) claim. You can obtain the {% data variables.product.prodname_github_app %} identifier via the initial webhook ping after [creating the app](/apps/building-github-apps/creating-a-github-app/), or at any time from the app settings page in the GitHub.com UI. From 3122275826cc4bd0082fb7663d76dd988e24a276 Mon Sep 17 00:00:00 2001 From: Laura Coursen Date: Fri, 10 Sep 2021 09:34:38 -0500 Subject: [PATCH 09/12] Add :nail_care: --- .../setting-up-code-scanning-for-a-repository.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index cd4724fa18..0dcd2a9774 100644 --- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -58,7 +58,7 @@ In the default {% data variables.product.prodname_codeql_workflow %}, {% data va ## Bulk set up of {% data variables.product.prodname_code_scanning %} -You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. For an example of a script that raises pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using Powershell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have Powershell and instead would like to use NodeJS. +You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. If you'd like to use a script to raise pull requests that add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using Powershell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have Powershell and instead would like to use NodeJS. ## Understanding the pull request checks From b425d715851b79e0b57c7377f9e05362226e9680 Mon Sep 17 00:00:00 2001 From: Laura Coursen Date: Fri, 10 Sep 2021 09:38:18 -0500 Subject: [PATCH 10/12] Add :nail_care: --- .../building-github-apps/authenticating-with-github-apps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/developers/apps/building-github-apps/authenticating-with-github-apps.md b/content/developers/apps/building-github-apps/authenticating-with-github-apps.md index 70a5269dbf..5d454070fe 100644 --- a/content/developers/apps/building-github-apps/authenticating-with-github-apps.md +++ b/content/developers/apps/building-github-apps/authenticating-with-github-apps.md @@ -89,7 +89,7 @@ jwt = JWT.encode(payload, private_key, "RS256") puts jwt ``` -`YOUR_PATH_TO_PEM` and `YOUR_APP_ID` are the values you must replace and make sure to enclose them in double quotes. +`YOUR_PATH_TO_PEM` and `YOUR_APP_ID` are the values you must replace. Make sure to enclose the values in double quotes. Use your {% data variables.product.prodname_github_app %}'s identifier (`YOUR_APP_ID`) as the value for the JWT [iss](https://tools.ietf.org/html/rfc7519#section-4.1.1) (issuer) claim. You can obtain the {% data variables.product.prodname_github_app %} identifier via the initial webhook ping after [creating the app](/apps/building-github-apps/creating-a-github-app/), or at any time from the app settings page in the GitHub.com UI. From 8178f8127e9231bc392e83f08f1ac1148223fd77 Mon Sep 17 00:00:00 2001 From: Laura Coursen Date: Fri, 10 Sep 2021 09:54:10 -0500 Subject: [PATCH 11/12] Version content about enterprise accounts --- .../removing-a-member-from-your-organization.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md index 8655272c0b..d4e7fb9feb 100644 --- a/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md +++ b/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md @@ -23,7 +23,7 @@ Only organization owners can remove members from an organization. **Warning:** When you remove members from an organization: - The paid license count does not automatically downgrade. To pay for fewer licenses after removing users from your organization, follow the steps in "[Downgrading your organization's paid seats](/articles/downgrading-your-organization-s-paid-seats)." - Removed members will lose access to private forks of your organization's private repositories, but they may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. -- In addition, for customers with [Enterprise Accounts](https://docs.github.com/en/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts), removed members will lose access to private forks of your organization's internal repositories in this manner when and only when the removed member is not a member of another organization under that Enterprise Account. +- {% ifversion fpt %}If your organization is owned by an enterprise account, removed{% else %}Removed{% endif %} members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization{% ifversion fpt %} owned by the same enterprise account. For more information, see "[About enterprise accounts](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts)."{% else %}.{% endif %} - Any organization invitations sent by a removed member, that have not been accepted, are cancelled and will not be accessible. {% endwarning %} @@ -34,7 +34,7 @@ Only organization owners can remove members from an organization. **Warning:** When you remove members from an organization: - Removed members will lose access to private forks of your organization's private repositories, but may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. - - In addition, for customers with [Enterprise Accounts](https://docs.github.com/en/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts), removed members will lose access to private forks of your organization's internal repositories in this manner when and only when the removed member is not a member of another organization under that Enterprise Account. +- {% ifversion fpt %}If your organization is owned by an enterprise account, removed{% else %}Removed{% endif %} members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization{% ifversion fpt %} owned by the same enterprise account. For more information, see "[About enterprise accounts](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts)."{% else %}.{% endif %} - Any organization invitations sent by the removed user, that have not been accepted, are cancelled and will not be accessible. {% endwarning %} From ffc45191e1e1a5d899f7f27ffbc8f10b70964ae2 Mon Sep 17 00:00:00 2001 From: Laura Coursen Date: Fri, 10 Sep 2021 09:56:35 -0500 Subject: [PATCH 12/12] Use existing versioning instead --- .../removing-a-member-from-your-organization.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md index d4e7fb9feb..41580aa8ea 100644 --- a/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md +++ b/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md @@ -23,7 +23,7 @@ Only organization owners can remove members from an organization. **Warning:** When you remove members from an organization: - The paid license count does not automatically downgrade. To pay for fewer licenses after removing users from your organization, follow the steps in "[Downgrading your organization's paid seats](/articles/downgrading-your-organization-s-paid-seats)." - Removed members will lose access to private forks of your organization's private repositories, but they may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. -- {% ifversion fpt %}If your organization is owned by an enterprise account, removed{% else %}Removed{% endif %} members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization{% ifversion fpt %} owned by the same enterprise account. For more information, see "[About enterprise accounts](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts)."{% else %}.{% endif %} +- If your organization is owned by an enterprise account, removed members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization owned by the same enterprise account. For more information, see "[About enterprise accounts](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts)." - Any organization invitations sent by a removed member, that have not been accepted, are cancelled and will not be accessible. {% endwarning %} @@ -34,7 +34,7 @@ Only organization owners can remove members from an organization. **Warning:** When you remove members from an organization: - Removed members will lose access to private forks of your organization's private repositories, but may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. -- {% ifversion fpt %}If your organization is owned by an enterprise account, removed{% else %}Removed{% endif %} members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization{% ifversion fpt %} owned by the same enterprise account. For more information, see "[About enterprise accounts](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts)."{% else %}.{% endif %} +- Removed members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization in your enterprise. - Any organization invitations sent by the removed user, that have not been accepted, are cancelled and will not be accessible. {% endwarning %}