Skip to content

Commit

Permalink
Merge branch 'main' into add-actions-performance-testing-numbers-ghes36
Browse files Browse the repository at this point in the history
  • Loading branch information
docubot authored Aug 16, 2022
2 parents 3271159 + bf0a426 commit 7bdefc8
Show file tree
Hide file tree
Showing 45 changed files with 177 additions and 33 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -12,39 +12,40 @@ miniTocMaxHeadingLevel: 3

## About accessibility settings

To accommodate your vision, hearing, motor, cognitive, or learning needs, you can customize the user interface for {% data variables.product.product_location %}.
To create an experience on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} 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.product_name %} clashes with another application shortcut.

## Managing accessibility settings

You can decide whether you want to use some or all keyboard shortcuts on {% ifversion fpt or ghec %}{% data variables.product.product_location %}{% elsif ghes or ghae %}the website for {% data variables.product.product_location %}{% endif %}, and you can control the display of animated images.

### Managing keyboard shortcuts

You can perform actions across the {% data variables.product.product_name %} website without using your mouse by using your keyboard instead. Keyboard shortcuts can be useful to save time for some people, but may interfere with accessibility if you don't intend to use the shortcuts.
You can perform actions across the {% data variables.product.product_name %} website by using your keyboard alone. Keyboard shortcuts can be useful to save time, but can be activated accidentally or interfere with assistive technology.

By default, all keyboard shortcuts are enabled on {% data variables.product.product_name %}. For more information, see "[Keyboard shortcuts](/get-started/using-github/keyboard-shortcuts)."

{% data reusables.user-settings.access_settings %}
{% data reusables.user-settings.accessibility_settings %}
1. Under "Keyboard shortcuts", manage settings for your keyboard shortcuts.

- Optionally, to disable or enable shortcut keys that don't use modifiers keys like <kbd>Control</kbd> or <kbd>Command</kbd>, under "General", deselect **Character keys**. If you disable character keys, you may still be able to trigger shortcuts for your web browser, and you can still trigger shortcuts for {% data variables.product.product_name %} that use a modifier key.
- To disable shortcut keys that don't use modifiers keys like <kbd>Control</kbd> or <kbd>Command</kbd>, under "General", deselect **Character keys**.
- If you disable character keys, you may still be able to trigger shortcuts for your web browser, and you can still trigger shortcuts for {% data variables.product.product_name %} that use a modifier key.
{%- ifversion command-palette %}
- Optionally, to customize the keyboard shortcuts for triggering the command palette, under "Command palette", use the drop-down menus to choose a keyboard shortcut. For more information, see "[{% data variables.product.company_short %} Command Palette](/get-started/using-github/github-command-palette)."
- To customize the keyboard shortcuts for triggering the command palette, under "Command palette", use the drop-down menus to choose a keyboard shortcut. For more information, see "[{% data variables.product.company_short %} Command Palette](/get-started/using-github/github-command-palette)."
{%- endif %}

{% ifversion motion-management %}

### Managing motion

You can control how {% data variables.product.product_name %} displays animated images.
You can control how {% data variables.product.product_name %} displays animated _.gif_ images.

By default, {% data variables.product.product_name %} syncs with your system-level preference for reduced motion. For more information, see the documentation or settings for your operating system.

{% data reusables.user-settings.access_settings %}
{% data reusables.user-settings.accessibility_settings %}
1. Under "Motion", manage settings for motion.

- Optionally, to control how {% data variables.product.product_name %} displays animaged images, under "Autoplay animated images", select **Sync with system**, **Enabled**, or **Disabled**.
- To control how {% data variables.product.product_name %} displays animated images, under "Autoplay animated images", select **Sync with system**, **Enabled**, or **Disabled**.

{% endif %}
{% endif %}
1 change: 1 addition & 0 deletions data/release-notes/enterprise-server/3-2/0.yml
Original file line number Diff line number Diff line change
Expand Up @@ -273,6 +273,7 @@ sections:
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'

deprecations:
- heading: Deprecation of GitHub Enterprise Server 2.21
Expand Down
1 change: 1 addition & 0 deletions data/release-notes/enterprise-server/3-2/1.yml
Original file line number Diff line number Diff line change
Expand Up @@ -25,3 +25,4 @@ sections:
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
1 change: 1 addition & 0 deletions data/release-notes/enterprise-server/3-2/10.yml
Original file line number Diff line number Diff line change
Expand Up @@ -13,3 +13,4 @@ sections:
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
1 change: 1 addition & 0 deletions data/release-notes/enterprise-server/3-2/11.yml
Original file line number Diff line number Diff line change
Expand Up @@ -41,3 +41,4 @@ sections:
- When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
1 change: 1 addition & 0 deletions data/release-notes/enterprise-server/3-2/12.yml
Original file line number Diff line number Diff line change
Expand Up @@ -21,3 +21,4 @@ sections:
- When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
1 change: 1 addition & 0 deletions data/release-notes/enterprise-server/3-2/13.yml
Original file line number Diff line number Diff line change
Expand Up @@ -25,3 +25,4 @@ sections:
- When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
1 change: 1 addition & 0 deletions data/release-notes/enterprise-server/3-2/14.yml
Original file line number Diff line number Diff line change
Expand Up @@ -20,3 +20,4 @@ sections:
- When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
1 change: 1 addition & 0 deletions data/release-notes/enterprise-server/3-2/15.yml
Original file line number Diff line number Diff line change
Expand Up @@ -17,3 +17,4 @@ sections:
- When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
9 changes: 9 additions & 0 deletions data/release-notes/enterprise-server/3-2/16.yml
Original file line number Diff line number Diff line change
Expand Up @@ -15,3 +15,12 @@ sections:
- The `ghe-set-password` command-line utility starts required services automatically when the instance is booted in recovery mode.
- Metrics for `aqueduct` background processes are gathered for Collectd forwarding and display in the Management Console.
- The location of the database migration and configuration run log, `/data/user/common/ghe-config.log`, is now displayed on the page that details a migration in progress.
known_issues:
- On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
- Custom firewall rules are removed during the upgrade process.
- Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
- Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
- When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
1 change: 1 addition & 0 deletions data/release-notes/enterprise-server/3-2/2.yml
Original file line number Diff line number Diff line change
Expand Up @@ -20,3 +20,4 @@ sections:
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
1 change: 1 addition & 0 deletions data/release-notes/enterprise-server/3-2/3.yml
Original file line number Diff line number Diff line change
Expand Up @@ -28,3 +28,4 @@ sections:
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
1 change: 1 addition & 0 deletions data/release-notes/enterprise-server/3-2/4.yml
Original file line number Diff line number Diff line change
Expand Up @@ -27,3 +27,4 @@ sections:
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
1 change: 1 addition & 0 deletions data/release-notes/enterprise-server/3-2/5.yml
Original file line number Diff line number Diff line change
Expand Up @@ -25,3 +25,4 @@ sections:
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
1 change: 1 addition & 0 deletions data/release-notes/enterprise-server/3-2/6.yml
Original file line number Diff line number Diff line change
Expand Up @@ -11,3 +11,4 @@ sections:
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
1 change: 1 addition & 0 deletions data/release-notes/enterprise-server/3-2/7.yml
Original file line number Diff line number Diff line change
Expand Up @@ -20,3 +20,4 @@ sections:
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
1 change: 1 addition & 0 deletions data/release-notes/enterprise-server/3-2/8.yml
Original file line number Diff line number Diff line change
Expand Up @@ -23,3 +23,4 @@ sections:
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
1 change: 1 addition & 0 deletions data/release-notes/enterprise-server/3-2/9.yml
Original file line number Diff line number Diff line change
Expand Up @@ -17,3 +17,4 @@ sections:
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
Loading

0 comments on commit 7bdefc8

Please sign in to comment.