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/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/index.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Managing user account settings
3
-
intro: 'You can manage settings for your personal account, including your theme, username, default branch, accessibility, and security settings.'
3
+
intro: You can manage settings for your personal account, including your theme, username, default branch, accessibility, and security settings.
Copy file name to clipboardExpand all lines: content/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-accessibility-settings.md
+4-13Lines changed: 4 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,13 +13,7 @@ redirect_from:
13
13
type: how_to
14
14
---
15
15
16
-
## About accessibility settings
17
-
18
-
To create an experience on {% data variables.product.github %} that fits your needs, you can customize the user interface. Accessibility settings can be essential for people with disabilities, but can be useful to anyone. For example, customization of keyboard shortcuts is essential to people who navigate using voice control, but can be useful to anyone when a keyboard shortcut for {% data variables.product.github %} clashes with another application shortcut.
19
-
20
-
You can decide whether you want to use some or all keyboard shortcuts, and control the display of animated images and how links are displayed.
21
-
22
-
This article will help you customize your experience on the {% data variables.product.github %} website as a whole. For information on using specific {% data variables.product.github %} products with screen readers and other assistive technologies, see the [{% data variables.product.github %} Accessibility Documentation](https://accessibility.github.com/documentation).
16
+
> [!NOTE] This article will help you customize your experience on the {% data variables.product.github %} website as a whole. For information on using specific {% data variables.product.github %} products with screen readers and other assistive technologies, see the [{% data variables.product.github %} Accessibility Documentation](https://accessibility.github.com/documentation).
23
17
24
18
## Managing the appearance of links
25
19
@@ -35,8 +29,6 @@ You can control whether links in text blocks are underlined and therefore more d
35
29
36
30
## Managing keyboard shortcuts
37
31
38
-
You can perform actions across the {% data variables.product.github %} website by using your keyboard alone. Keyboard shortcuts can be useful to save time, but can be activated accidentally or interfere with assistive technology.
39
-
40
32
By default, all keyboard shortcuts are enabled. For more information, see [AUTOTITLE](/get-started/accessibility/keyboard-shortcuts).
41
33
42
34
{% data reusables.user-settings.access_settings %}
@@ -65,7 +57,6 @@ By default, {% data variables.product.github %} syncs with your system-level pre
65
57
66
58
You can customize contrast levels to improve visibility and meet accessibility needs.
67
59
68
-
* If you're **not signed in**, click {% octicon "sliders" aria-hidden="true" aria-label="sliders" %} on the right in the top navigation bar to access the contrast settings.
69
-
* If you're **signed in**, click **{% octicon "paintbrush" aria-hidden="true" aria-label="paintbrush" %} Appearance** in the left sidebar of your user settings. Under "Contrast", you can access the contrast settings.
70
-
71
-
You can toggle the switch for "Increase contrast" to enable or disable high contrast mode. You can also choose between light and dark mode, or both, based on your system settings.
60
+
1. If you're **not signed in**, click {% octicon "sliders" aria-hidden="true" aria-label="sliders" %} on the right in the top navigation bar to access the contrast settings.
61
+
1. If you're **signed in**, click **{% octicon "paintbrush" aria-hidden="true" aria-label="paintbrush" %} Appearance** in the left sidebar of your user settings.
62
+
1. Under "Contrast", toggle the "Increase contrast" switch.
## About management of security and analysis settings
19
20
20
-
{% data variables.product.prodname_dotcom %} can help secure your repositories. This topic tells you how you can manage the security and analysis features for all your existing or new repositories.
21
-
22
-
You can still manage the security and analysis features for individual repositories. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository).
23
-
24
-
You can also review the security log for all activity on your personal account. For more information, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log).
25
-
26
-
{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
27
-
28
-
{% data reusables.security.security-and-analysis-features-enable-read-only %}
29
-
30
-
For an overview of repository-level security, see [AUTOTITLE](/code-security/getting-started/securing-your-repository).
21
+
> [!NOTE] This topic tells you how you can manage the security and analysis features for all your existing or new repositories. For information on managing these settings for individual repositories, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository).
31
22
32
23
## Enabling or disabling features for existing repositories
33
24
@@ -40,16 +31,12 @@ For an overview of repository-level security, see [AUTOTITLE](/code-security/get
40
31
41
32
1. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories you own.
42
33
43
-
{% data reusables.security.displayed-information %}
44
-
45
34
## Enabling or disabling features for new repositories
46
35
47
36
{% data reusables.user-settings.access_settings %}
48
37
{% data reusables.user-settings.security-analysis %}
49
38
1. Under "{% data variables.product.UI_advanced_security %}", to the right of the feature, enable or disable the feature by default for new repositories that you own.
When you select **Available for hire** and someone uses the REST API to get public and private information about authenticated users, the `hireable` field returns `true`. For more information, see [AUTOTITLE](/rest/users/users) in the REST API documentation.
21
-
22
22
{% data reusables.user-settings.access_settings %}
23
23
24
24
1. Under Jobs Profile, select **Available for hire**, then click **Save jobs profile**.
25
+
26
+
## Next steps
27
+
28
+
For reference information, see [AUTOTITLE](/account-and-profile/reference/personal-account-reference#available-for-hire).
Copy file name to clipboardExpand all lines: content/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/changing-your-username.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ topics:
9
9
- Accounts
10
10
- Usernames
11
11
shortTitle: Change username
12
-
permissions: '{% ifversion ghec %}Users with personal accounts can change their username. Members of an {% data variables.enterprise.prodname_emu_enterprise %} cannot change their username.{% elsif ghes %}If your instance uses built-in authentication, you can change your username. If you sign in to {% data variables.location.product_location %} with LDAP credentials or single sign-on (SSO), only your local administrator can change your username.{% else %}Users with personal accounts can change their username.{% endif %}'
12
+
permissions: '{% ifversion ghec %}Users with personal accounts can change their username. Members of an {% data variables.enterprise.prodname_emu_enterprise %} cannot change their username.{% elsif ghes %}If your instance uses built-in authentication or LDAP, you can change your username. If you sign in to {% data variables.location.product_location %} with single sign-on (SSO), only your local administrator can change your username.{% else %}Users with personal accounts can change their username.{% endif %}'
Copy file name to clipboardExpand all lines: content/account-and-profile/reference/personal-account-reference.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,3 +47,15 @@ versions:
47
47
* Any commits authored with a {% data variables.product.company_short %}-provided `noreply` email address cannot be transferred from one account to another. If the account you want to delete used the **Keep my email address private** option, it won't be possible to transfer the commits authored by the account you are deleting to the account you want to keep.
48
48
* Issues, pull requests, and discussions will not be attributed to the new account.
49
49
* Achievements are not able to be transferred between accounts.
50
+
51
+
## Security and analysis features settings
52
+
53
+
{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
54
+
55
+
{% data reusables.security.security-and-analysis-features-enable-read-only %}
56
+
57
+
{% data reusables.security.displayed-information %}
58
+
59
+
## Available for hire
60
+
61
+
When you select that you are **Available for hire** and someone uses the REST API to get public and private information about authenticated users, the `hireable` field returns `true`. For more information, see [AUTOTITLE](/rest/users/users) in the REST API documentation.
Rather than copying and pasting from one workflow to another, you can make workflows reusable. You and anyone with access to the reusable workflow can then call the reusable workflow from another workflow.
17
19
@@ -33,7 +35,7 @@ If you reuse a workflow from a different repository, any actions in the called w
33
35
34
36
You can view the reused workflows referenced in your {% data variables.product.prodname_actions %} workflows as dependencies in the dependency graph of the repository containing your workflows. For more information, see “[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).”
35
37
36
-
## Reusable workflows versus composite actions
38
+
###Reusable workflows versus composite actions
37
39
38
40
Reusable workflows and composite actions both help you avoid duplicating workflow content. Whereas reusable workflows allow you to reuse an entire workflow, with multiple jobs and steps, composite actions combine multiple steps that you can then run within a job step, just like any other action.
39
41
@@ -57,7 +59,7 @@ Let's compare some aspects of each solution:
57
59
| Can connect a maximum of four levels of workflows | Can be nested to have up to 10 composite actions in one workflow |
58
60
| Can use secrets | Cannot use secrets |
59
61
60
-
## Reusable workflows and workflow templates
62
+
## Workflow templates
61
63
62
64
Workflow templates allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When people create a new workflow, they can choose a workflow template and some or all of the work of writing the workflow will be done for them. Within a workflow template, you can also reference reusable workflows to make it easy for people to benefit from reusing centrally managed workflow code.
63
65
@@ -71,6 +73,16 @@ If you use a commit SHA when referencing the reusable workflow, you can ensure t
71
73
72
74
For more information, see [AUTOTITLE](/actions/using-workflows/creating-starter-workflows-for-your-organization).
73
75
76
+
{% ifversion fpt or ghec %}
77
+
78
+
## YAML anchors and aliases
79
+
80
+
You can use YAML anchors and aliases to reduce repetition in your workflows. An anchor (marked with `&`) identifies a piece of content that you want to reuse, while an alias (marked with `*`) repeats that content in another location. Think of an anchor as creating a named template and an alias as using that template. This is particularly useful when you have jobs or steps that share common configurations.
81
+
82
+
For reference information and examples, see [AUTOTITLE](/actions/reference/workflows-and-actions/reusing-workflow-configurations#yaml-anchors-and-aliases).
83
+
84
+
{% endif %}
85
+
74
86
## Next steps
75
87
76
88
To start reusing your workflows, see [AUTOTITLE](/actions/how-tos/sharing-automations/reuse-workflows).
0 commit comments