You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md
+11-9
Original file line number
Diff line number
Diff line change
@@ -11,31 +11,33 @@ intro: You can convert your personal account into an organization. This allows m
11
11
versions:
12
12
fpt: '*'
13
13
ghes: '*'
14
+
ghae: '*'
14
15
ghec: '*'
15
16
topics:
16
17
- Accounts
17
18
shortTitle: User into an organization
18
19
---
19
20
{% warning %}
20
21
21
-
**Warning**: Before converting a user into an organization, keep these points in mind:
22
-
23
-
- You will **no longer** be able to sign into the converted personal account.
24
-
- You will **no longer** be able to create or modify gists owned by the converted personal account.
25
-
- An organization **cannot** be converted back to a user.
26
-
- The SSH keys, OAuth tokens, job profile, reactions, and associated user information, **will not** be transferred to the organization. This is only true for the personal account that's being converted, not any of the personal account's collaborators.
27
-
- Any commits made with the converted personal account **will no longer be linked** to that account. The commits themselves **will** remain intact.
28
-
- Any forks of private repositories made with the converted personal account will be deleted.
22
+
**Warning**: Before converting a user into an organization, keep these points in mind.
29
23
24
+
* You will **no longer** be able to sign into the converted personal account.
25
+
* You will **no longer** be able to create or modify gists owned by the converted personal account.
26
+
* An organization **cannot** be converted back to a user.
27
+
* The SSH keys, OAuth tokens, job profile, reactions, and associated user information, **will not** be transferred to the organization. This is only true for the personal account that's being converted, not any of the personal account's collaborators.
28
+
* Any commits made with the converted personal account **will no longer be linked** to that account. The commits themselves **will** remain intact.
29
+
* Any existing comments made by the converted personal account **will no longer be linked** to that account. The comments themselves **will** remain intact, but will be associated with the `ghost` user.
30
+
* Any forks of private repositories made with the converted personal account will be deleted.
30
31
{% endwarning %}
31
32
33
+
{% ifversion fpt or ghec or ghes %}
32
34
## Keep your personal account and create a new organization manually
33
35
34
36
If you want your organization to have the same name that you are currently using for your personal account, or if you want to keep your personal account's information intact, then you must create a new organization and transfer your repositories to it instead of converting your personal account into an organization.
35
37
36
38
1. To retain your current personal account name for your personal use, [change the name of your personal account](/articles/changing-your-github-username) to something new and wonderful.
37
39
2.[Create a new organization](/articles/creating-a-new-organization-from-scratch) with the original name of your personal account.
38
-
3.[Transfer your repositories](/articles/transferring-a-repository) to your new organization account.
40
+
3.[Transfer your repositories](/articles/transferring-a-repository) to your new organization account.{% endif %}
39
41
40
42
## Convert your personal account into an organization automatically
Copy file name to clipboardExpand all lines: content/actions/creating-actions/about-custom-actions.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -88,7 +88,7 @@ This section explains how you can use release management to distribute updates t
88
88
89
89
### Good practices for release management
90
90
91
-
If you're developing an action for other people to use, we recommend using release management to control how you distribute updates. Users can expect an action's major version to include necessary critical fixes and security patches, while still remaining compatible with their existing workflows. You should consider releasing a new major version whenever your changes affect compatibility.
91
+
If you're developing an action for other people to use, we recommend using release management to control how you distribute updates. Users can expect an action's patch version to include necessary critical fixes and security patches, while still remaining compatible with their existing workflows. You should consider releasing a new major version whenever your changes affect compatibility.
92
92
93
93
Under this release management approach, users should not be referencing an action's default branch, as it's likely to contain the latest code and consequently might be unstable. Instead, you can recommend that your users specify a major version when using your action, and only direct them to a more specific version if they encounter issues.
Copy file name to clipboardExpand all lines: content/admin/code-security/index.md
-1
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,6 @@ shortTitle: Manage code security
4
4
intro: 'You can build security into your developers'' workflow with features that keep secrets and vulnerabilities out of your codebase, and that maintain your software supply chain.'
0 commit comments