Use existing versioning instead
This commit is contained in:
@@ -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 %}
|
||||
|
||||
Reference in New Issue
Block a user