From 0371abe11535ed13ff43d73c1f02fd96406936b6 Mon Sep 17 00:00:00 2001 From: Laura Coursen Date: Tue, 9 May 2023 09:36:45 -0500 Subject: [PATCH] Hide decorative octicons (#36816) Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com> --- .../managing-your-tab-size-rendering-preference.md | 2 +- ...ssing-compliance-reports-for-your-enterprise.md | 2 +- ...or-personal-access-tokens-in-your-enterprise.md | 6 +++--- .../restoring-a-deleted-repository.md | 2 +- ...g-membership-information-for-your-enterprise.md | 2 +- .../viewing-people-in-your-enterprise.md | 4 ++-- .../creating-a-personal-access-token.md | 4 ++-- .../reviewing-your-deploy-keys.md | 2 +- .../reviewing-your-security-log.md | 2 +- .../viewing-your-github-advanced-security-usage.md | 4 ++-- .../viewing-your-github-copilot-usage.md | 2 +- .../connecting-an-azure-subscription.md | 4 ++-- .../about-billing-on-github.md | 4 ++-- ...nterprise-server-and-github-enterprise-cloud.md | 2 +- .../troubleshooting-the-codeql-workflow.md | 4 ++-- ...roubleshooting-your-default-setup-for-codeql.md | 4 ++-- .../viewing-code-scanning-logs.md | 3 +-- .../getting-started/securing-your-repository.md | 4 ++-- .../managing-alerts-from-secret-scanning.md | 4 ++-- ...guring-automatic-deletion-of-your-codespaces.md | 2 +- .../creating-a-codespace-for-a-repository.md | 10 +++++----- .../creating-a-codespace-from-a-template.md | 2 +- .../deleting-a-codespace.md | 2 +- .../using-github-codespaces-for-pull-requests.md | 4 ++-- .../about-github-codespaces-prebuilds.md | 2 +- .../introduction-to-dev-containers.md | 2 +- ...-quick-creation-and-resumption-of-codespaces.md | 8 ++++---- .../exporting-changes-to-a-branch.md | 4 ++-- .../troubleshooting/troubleshooting-prebuilds.md | 10 +++++----- ...github-copilot-settings-in-your-organization.md | 2 +- .../syncing-your-branch-in-github-desktop.md | 2 +- ...ng-changes-to-your-project-in-github-desktop.md | 3 +-- .../managing-branches-in-github-desktop.md | 4 ++-- .../cherry-picking-a-commit-in-github-desktop.md | 2 +- ...wing-and-re-running-checks-in-github-desktop.md | 2 +- .../managing-discussions.md | 14 +++++++------- ...tting-started-with-github-community-exchange.md | 2 +- ...sing-github-codespaces-with-github-classroom.md | 2 +- .../editing-an-assignment.md | 2 +- .../reuse-an-assignment.md | 2 +- .../use-the-git-and-github-starter-assignment.md | 2 +- content/get-started/using-github/github-mobile.md | 6 +++--- .../creating-a-permanent-link-to-a-code-snippet.md | 2 +- content/graphql/overview/public-schema.md | 6 +++--- .../creating-a-project-board.md | 2 +- ...-issues-and-pull-requests-to-a-project-board.md | 4 ++-- .../migrating-from-projects-classic.md | 8 ++++---- .../customizing-the-roadmap-layout.md | 2 +- .../quickstart-for-projects.md | 6 +++--- .../adding-your-project-to-a-repository.md | 2 +- .../creating-an-issue.md | 2 +- ...ing-compliance-reports-for-your-organization.md | 2 +- ...team-access-to-an-organization-project-board.md | 5 +++-- ...ject-visibility-changes-in-your-organization.md | 4 ++-- ...imiting-github-actions-for-your-organization.md | 2 +- ...ng-pull-request-reviews-in-your-organization.md | 2 +- ...-personal-access-tokens-in-your-organization.md | 5 ++--- ...-personal-access-tokens-in-your-organization.md | 6 +++--- ...al-access-token-policy-for-your-organization.md | 6 +++--- .../managing-code-review-settings-for-your-team.md | 4 ++-- .../learn-github-packages/viewing-packages.md | 2 +- ...erifying-your-custom-domain-for-github-pages.md | 4 ++-- ...ing-the-visibility-of-your-github-pages-site.md | 5 +++-- ...ing-github-actions-settings-for-a-repository.md | 8 ++++---- .../configuring-tag-protection-rules.md | 4 ++-- .../downloading-source-code-archives.md | 4 ++-- .../github-code-search/using-github-code-search.md | 2 +- ...ttributing-sponsorships-to-your-organization.md | 2 +- ...sted-runners-navigate-to-repo-org-enterprise.md | 2 +- .../settings-ui/settings-actions-runner-groups.md | 2 +- .../settings-ui/settings-actions-runners.md | 2 +- .../actions/sidebar-secrets-and-variables.md | 2 +- .../assignments-guide-create-the-assignment.md | 2 +- data/reusables/classroom/click-settings.md | 2 +- data/reusables/classroom/click-students.md | 2 +- .../codespaces/codespaces-org-policies.md | 2 +- .../codespaces/navigating-to-a-codespace.md | 2 +- data/reusables/codespaces/sidebar-secret.md | 2 +- .../copilot/disable-copilot-organization.md | 2 +- data/reusables/copilot/signup-procedure.md | 2 +- data/reusables/dependabot/sidebar-secret.md | 2 +- .../desktop/click-base-branch-in-drop-down.md | 2 +- data/reusables/desktop/current-branch-menu.md | 2 +- .../desktop/navigate-to-stashed-changes.md | 2 +- data/reusables/desktop/select-branch-to-delete.md | 2 +- data/reusables/discussions/discussions-tab.md | 2 +- data/reusables/discussions/starting-a-poll.md | 2 +- data/reusables/enterprise-accounts/actions-tab.md | 2 +- data/reusables/enterprise-accounts/copilot-tab.md | 2 +- data/reusables/enterprise-accounts/options-tab.md | 2 +- data/reusables/enterprise-accounts/pages-tab.md | 2 +- data/reusables/organizations/billing-settings.md | 4 ++-- data/reusables/organizations/billing_plans.md | 2 +- data/reusables/organizations/block_users.md | 2 +- data/reusables/organizations/click-codespaces.md | 2 +- data/reusables/organizations/compliance.md | 2 +- .../organizations/github-apps-settings-sidebar.md | 2 +- .../reusables/organizations/mixed-roles-warning.md | 2 +- .../organizations/org-settings-repository-roles.md | 2 +- data/reusables/organizations/teams_sidebar.md | 2 +- data/reusables/pages/sidebar-pages.md | 2 +- data/reusables/pages/visit-site.md | 2 +- data/reusables/project-management/click-menu.md | 2 +- .../link-repos-to-project-board.md | 2 +- data/reusables/projects/access-workflows.md | 4 ++-- data/reusables/projects/customize/sort.md | 6 +++--- data/reusables/projects/customize/sum.md | 2 +- data/reusables/reminders/scheduled-reminders.md | 2 +- data/reusables/repositories/actions-cache-list.md | 2 +- data/reusables/repositories/actions-tab.md | 2 +- data/reusables/repositories/changed-files.md | 2 +- data/reusables/repositories/review-pr-commits.md | 2 +- .../sidebar-moderation-reported-content.md | 2 +- .../repositories/sidebar-notifications.md | 2 +- .../reusables/user-settings/access_applications.md | 2 +- .../user-settings/accessibility_settings.md | 2 +- data/reusables/user-settings/account_settings.md | 2 +- .../reusables/user-settings/appearance-settings.md | 2 +- data/reusables/user-settings/billing_plans.md | 2 +- .../user-settings/billing_plans_payment.md | 2 +- .../user-settings/billing_plans_spending.md | 2 +- data/reusables/user-settings/blocked_users.md | 2 +- data/reusables/user-settings/codespaces-tab.md | 2 +- data/reusables/user-settings/copilot-settings.md | 2 +- data/reusables/user-settings/emails.md | 2 +- data/reusables/user-settings/organizations.md | 2 +- data/reusables/user-settings/repo-tab.md | 2 +- data/reusables/user-settings/saved_replies.md | 2 +- data/reusables/user-settings/security-analysis.md | 2 +- data/reusables/user-settings/security.md | 2 +- data/reusables/user-settings/sessions.md | 2 +- data/reusables/user-settings/ssh.md | 2 +- 132 files changed, 194 insertions(+), 195 deletions(-) diff --git a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md index 3b5823d89c..b9769ef3e1 100644 --- a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md @@ -16,5 +16,5 @@ redirect_from: If you feel that tabbed indentation in code rendered on {% data variables.product.product_name %} takes up too much, or too little space, you can change this in your settings. {% data reusables.user-settings.access_settings %} -1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**. +1. In the left sidebar, click **{% octicon "paintbrush" aria-hidden="true" %} Appearance**. 2. Scroll down to "Tab size preference" and use the dropdown menu to choose your preference. \ No newline at end of file diff --git a/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md b/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md index 538ca73940..82facea68f 100644 --- a/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md +++ b/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md @@ -22,7 +22,7 @@ You can access {% data variables.product.company_short %}'s compliance reports i {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %} -1. Under "Resources", to the right of the report you want to access, click {% octicon "download" aria-label="The Download icon" %} **Download** or {% octicon "link-external" aria-label="The external link icon" %} **View**. +1. Under "Resources", to the right of the report you want to access, click {% octicon "download" aria-hidden="true" %} **Download** or {% octicon "link-external" aria-hidden="true" %} **View**. {% data reusables.security.compliance-report-screenshot %} diff --git a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise.md b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise.md index 69ce848fb3..8662c5c298 100644 --- a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise.md +++ b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise.md @@ -22,7 +22,7 @@ Enterprise owners can prevent {% data variables.product.pat_v2 %}s from accessin {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} -1. Under {% octicon "law" aria-label="The law icon" %} **Policies**, click **Organizations**. +1. Under {% octicon "law" aria-hidden="true" %} **Policies**, click **Organizations**. 1. Under **Restrict access via {% data variables.product.pat_v2 %}s**, select the option that meets your needs: - **Allow organizations to configure access requirements**: Each organization owned by the enterprise can decide whether to restrict access by {% data variables.product.pat_v2 %}s. - **Restrict access via {% data variables.product.pat_v2 %}s**: {% data variables.product.pat_v2_caps %}s cannot access organizations owned by the enterprise. SSH keys created by {% data variables.product.pat_v2 %}s will continue to work. Organizations cannot override this setting. @@ -41,7 +41,7 @@ Enterprise owners can require that all organizations owned by the enterprise mus {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} -1. Under {% octicon "law" aria-label="The law icon" %} **Policies**, click **Organizations**. +1. Under {% octicon "law" aria-hidden="true" %} **Policies**, click **Organizations**. 1. Under **Require approval of {% data variables.product.pat_v2 %}s**, select the option that meets your needs: - **Allow organizations to configure approval requirements**: Each organization owned by the enterprise can decide whether to require approval of {% data variables.product.pat_v2 %} that can access the organization. - **Require organizations to use the approval flow**: All organizations owned by the enterprise must approve each {% data variables.product.pat_v2 %} that can access the organization. {% data variables.product.pat_v2_caps %}s created by organization owners will not need approval. Organizations cannot override this setting. @@ -54,7 +54,7 @@ Enterprise owners can prevent {% data variables.product.pat_v1_plural %} from ac {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} -1. Under {% octicon "law" aria-label="The law icon" %} **Policies**, click **Organizations**. +1. Under {% octicon "law" aria-hidden="true" %} **Policies**, click **Organizations**. 1. Under **Restrict {% data variables.product.pat_v1_plural %} from accessing your organizations**, select the option that meets your needs: - **Allow organizations to configure {% data variables.product.pat_v1_plural %} access requirements**: Each organization owned by the enterprise can decide whether to restrict access by {% data variables.product.pat_v1_plural %}. - **Restrict access via {% data variables.product.pat_v1_plural %}**: {% data variables.product.pat_v1_caps_plural %} cannot access the enterprise or organizations owned by the enterprise. SSH keys created by {% data variables.product.pat_v1_plural %} will continue to work. Organizations cannot override this setting. diff --git a/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md b/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md index 5c494c962e..4112de99c6 100644 --- a/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md +++ b/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md @@ -29,7 +29,7 @@ Restoring a repository will not restore release attachments or team permissions. {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.search-user-or-org %} {% data reusables.enterprise_site_admin_settings.click-user-or-org %} -1. In the {% octicon "repo" aria-label="The repo icon" %} **Repositories** section, click the {% octicon "trash" aria-label="The trash icon" %} **Deleted repositories** link. +1. In the {% octicon "repo" aria-hidden="true" %} **Repositories** section, click the {% octicon "trash" aria-hidden="true" %} **Deleted repositories** link. 1. Find the repository you want to restore in the deleted repositories list, then to the right of the repository name click **Restore**. 1. To confirm you would like to restore the named repository, click **Restore**. diff --git a/content/admin/user-management/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise.md b/content/admin/user-management/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise.md index 077899ee0b..0ef886eb38 100644 --- a/content/admin/user-management/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise.md +++ b/content/admin/user-management/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise.md @@ -36,7 +36,7 @@ You can download a CSV file containing the membership information report for you {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} -1. To the right of "Members", click **{% octicon "download" aria-label="The download icon" %} CSV Report**. +1. To the right of "Members", click **{% octicon "download" aria-hidden="true" %} CSV Report**. - If your enterprise has less than 1,000 members, the report will download immediately. - If your enterprise has 1,000 or more members, you'll soon receive an email with a link to download the report. diff --git a/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md index 0796df3cab..6aff81ca04 100644 --- a/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md +++ b/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md @@ -140,7 +140,7 @@ If your enterprise uses {% data variables.product.prodname_emus %}, you can view {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} -1. Under "People", click **Suspended**. +1. Under "People", click **Suspended**. {% endif %} @@ -172,7 +172,7 @@ You can view a list of members in your enterprise who don't have an email addres {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.verified-domains-tab %} -1. Under "Notification preferences", click the {% octicon "eye" aria-label="The github eye icon" %} **View enterprise members without an approved or verified domain email** link. +1. Under "Notification preferences", click the {% octicon "eye" aria-hidden="true" %} **View enterprise members without an approved or verified domain email** link. {% endif %} ## Further reading diff --git a/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md index 81dc4a236a..5a8b1b6fc8 100644 --- a/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md +++ b/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md @@ -90,7 +90,7 @@ When using a {% data variables.product.pat_generic %} in a script, you can store {% ifversion fpt or ghec %}1. [Verify your email address](/get-started/signing-up-for-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %} {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} -1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Fine-grained tokens**. +1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Fine-grained tokens**. 1. Click **Generate new token**. 1. Under **Token name**, enter a name for the token. 1. Under **Expiration**, select an expiration for the token. @@ -131,7 +131,7 @@ If you selected an organization as the resource owner and the organization requi {% ifversion fpt or ghec %}1. [Verify your email address](/get-started/signing-up-for-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %} {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} -{% ifversion pat-v2 %}1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Tokens (classic)**.{% else %}{% data reusables.user-settings.personal_access_tokens %}{% endif %} +{% ifversion pat-v2 %}1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Tokens (classic)**.{% else %}{% data reusables.user-settings.personal_access_tokens %}{% endif %} {% ifversion pat-v2%}1. Select **Generate new token**, then click **Generate new token (classic)**.{% else %}{% data reusables.user-settings.generate_new_token %}{% endif %} 5. In the "Note" field, give your token a descriptive name. 6. To give your token an expiration, select **Expiration**, then choose a default option or click **Custom** to enter a date. diff --git a/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md b/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md index 9ff0816e6d..ba3b62e2d2 100644 --- a/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md +++ b/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md @@ -18,7 +18,7 @@ shortTitle: Deploy keys {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -3. In the "Security" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} Deploy keys**. +3. In the "Security" section of the sidebar, click **{% octicon "key" aria-hidden="true" %} Deploy keys**. {% else %} 3. In the left sidebar, click **Deploy keys**. {% endif %} diff --git a/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md index 30ada4b2d9..4da7673be9 100644 --- a/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md +++ b/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md @@ -22,7 +22,7 @@ The security log lists all actions performed within the last 90 days. {% data reusables.user-settings.access_settings %} {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**. +1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-hidden="true" %} Security log**. {% else %} 1. In the user settings sidebar, click **Security log**. {% endif %} diff --git a/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md b/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md index 72cb92dcdd..a2c404024b 100644 --- a/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md +++ b/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md @@ -87,7 +87,7 @@ You can download the {% data variables.product.prodname_advanced_security %} lic {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the "Security" section of the sidebar, click {% octicon "codescan" aria-label="The {% data variables.product.prodname_code_scanning %} icon" %} **Code security and analysis**. +1. In the "Security" section of the sidebar, click {% octicon "codescan" aria-hidden="true" %} **Code security and analysis**. 1. In the "{% data variables.product.prodname_GH_advanced_security %} repositories" section, next to the repository you want usage information for, select {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Download CSV report**. ![Screenshot of the committers by repository table. The horizontal kebab icon and "Download CSV report" button are highlighted with an orange outline.](/assets/images/help/billing/ghas-billing-table-repository-csv.png) @@ -99,7 +99,7 @@ You can download the {% data variables.product.prodname_advanced_security %} lic {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.billing_plans %} -1. Underneath "{% data variables.product.prodname_GH_advanced_security %}," next to "Committers", click **{% octicon "download" aria-label="The download icon" %} CSV report**. +1. Underneath "{% data variables.product.prodname_GH_advanced_security %}," next to "Committers", click **{% octicon "download" aria-hidden="true" %} CSV report**. {% endif %} {% ifversion ghas-billing-table-ui-update %} diff --git a/content/billing/managing-billing-for-github-copilot/viewing-your-github-copilot-usage.md b/content/billing/managing-billing-for-github-copilot/viewing-your-github-copilot-usage.md index 682814d8cf..2e256a2a2f 100644 --- a/content/billing/managing-billing-for-github-copilot/viewing-your-github-copilot-usage.md +++ b/content/billing/managing-billing-for-github-copilot/viewing-your-github-copilot-usage.md @@ -33,7 +33,7 @@ The spending information will display the total spending for each organization f {% endif %} {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**. +1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**. 1. Under "{% data variables.product.prodname_copilot_short %}", view the breakdown of your {% data variables.product.prodname_copilot %} usage and upcoming changes in your organization. ![Screenshot of the organization-level {% data variables.product.prodname_copilot %} seat usage page](/assets/images/help/copilot/org-level-seat-view.png) diff --git a/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription.md b/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription.md index b3c5efa1f7..2bbab25299 100644 --- a/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription.md +++ b/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription.md @@ -34,7 +34,7 @@ To connect your Azure subscription, you must have owner permissions to the subsc {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**. +1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**. 1. Under "Billing Management", to the right of "Metered billing via Azure", click **Add Azure Subscription**. 1. To sign in to your Microsoft account, follow the prompts. 1. Review the "Permissions requested" prompt. If you agree with the terms, click **Accept**. @@ -77,7 +77,7 @@ After you disconnect your Azure subscription from your organization account, you {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**. +1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**. 1. Under "Billing Management", then under "Metered billing via Azure", to the right of the subscription ID you want to disconnect, click **{% octicon "trash" aria-label="The trash icon" %}**. 1. Review the prompt, then click **Remove**. diff --git a/content/billing/managing-your-github-billing-settings/about-billing-on-github.md b/content/billing/managing-your-github-billing-settings/about-billing-on-github.md index 1a7c9e1562..1cd4ce59cb 100644 --- a/content/billing/managing-your-github-billing-settings/about-billing-on-github.md +++ b/content/billing/managing-your-github-billing-settings/about-billing-on-github.md @@ -38,10 +38,10 @@ If you're an organization or enterprise owner, you can switch between settings f {% data reusables.user-settings.access_settings %} 1. At the top of the page, to the right of your name, click **Switch to another account**. - + ![Screenshot of the "Public profile" settings page for The Octocat. Next to the text "Your personal profile," a link, labeled "Switch to another account," is outlined in orange.](/assets/images/help/settings/context-switcher-button.png) 1. Start typing the name of the account you want to switch to, then click the name of the account. -1. In the left sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**. +1. In the left sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**. ## Further reading diff --git a/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md b/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md index 8efc1d2a0b..67c8bb837b 100644 --- a/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md +++ b/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md @@ -41,7 +41,7 @@ After you enable {% data variables.product.prodname_github_connect %}, license d {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -1. Under "License sync", click {% octicon "sync" aria-label="The Sync icon" %} **Sync now**. +1. Under "License sync", click {% octicon "sync" aria-hidden="true" %} **Sync now**. {% endif %} diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md index b15a5907b4..e6876a4211 100644 --- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md +++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md @@ -74,9 +74,9 @@ You can create {% data variables.product.prodname_codeql %} debugging artifacts If your {% data variables.product.prodname_code_scanning %} results are different than you expected, your repository may have both default and advanced {% data variables.product.prodname_code_scanning %} setups. When you enable default setup, this disables the existing {% data variables.product.prodname_codeql %} workflow file and blocks any {% data variables.product.prodname_codeql %} API analysis from uploading results. -To check if default setup is enabled, navigate to the main page of the repository, then click {% octicon "gear" aria-label="The gear icon" %} **Settings**. In the "Security" section of the sidebar, click {% octicon "codescan" aria-label="The {% data variables.product.prodname_code_scanning %} icon" %} **Code security and analysis**. In the "{% data variables.product.prodname_code_scanning_caps %}" section of the page, next to "{% data variables.product.prodname_codeql %} analysis," click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. If there is a {% octicon "workflow" aria-label="The workflow icon" %} **Switch to advanced** option, you are currently using the default setup. +To check if default setup is enabled, navigate to the main page of the repository, then click {% octicon "gear" aria-hidden="true" %} **Settings**. In the "Security" section of the sidebar, click {% octicon "codescan" aria-hidden="true" %} **Code security and analysis**. In the "{% data variables.product.prodname_code_scanning_caps %}" section of the page, next to "{% data variables.product.prodname_codeql %} analysis," click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. If there is a {% octicon "workflow" aria-hidden="true" %} **Switch to advanced** option, you are currently using the default setup. -If you want to return to using advanced setup and get {% data variables.product.prodname_code_scanning %} results from your custom workflow file, click {% octicon "stop" aria-label="The stop icon" %} **Disable {% data variables.product.prodname_codeql %}** to disable default setup. Then you should re-enable your pre-existing workflows to start triggering and uploading results from advanced setup. For more information, see "[AUTOTITLE](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)" and "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning-for-a-repository#creating-an-advanced-setup)." +If you want to return to using advanced setup and get {% data variables.product.prodname_code_scanning %} results from your custom workflow file, click {% octicon "stop" aria-hidden="true" %} **Disable {% data variables.product.prodname_codeql %}** to disable default setup. Then you should re-enable your pre-existing workflows to start triggering and uploading results from advanced setup. For more information, see "[AUTOTITLE](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)" and "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning-for-a-repository#creating-an-advanced-setup)." {% ifversion remove-code-scanning-configurations %} {% data reusables.code-scanning.troubleshooting-multiple-configurations %} diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-your-default-setup-for-codeql.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-your-default-setup-for-codeql.md index d3b667143f..7a1d47c2e5 100644 --- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-your-default-setup-for-codeql.md +++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-your-default-setup-for-codeql.md @@ -14,7 +14,7 @@ topics: - Troubleshooting --- -## A pre-existing {% data variables.product.prodname_codeql %} workflow is disabled +## A pre-existing {% data variables.product.prodname_codeql %} workflow is disabled If you see two workflows named **{% data variables.product.prodname_codeql %}**, one workflow may be a pre-existing {% data variables.product.prodname_codeql %} workflow file which has been disabled by default setup. Default setup overrides existing {% data variables.product.prodname_codeql %} setups by disabling any existing {% data variables.product.prodname_codeql %} workflows, and blocking any {% data variables.product.prodname_codeql %} analysis API uploads. This behavior stops you using {% data variables.product.prodname_actions %} minutes to run workflows for {% data variables.product.prodname_codeql %} advanced setup when only the results from default setup will be used. For more information about switching between advanced and default setups, see "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow#results-are-different-than-expected)." @@ -24,7 +24,7 @@ Optionally, if you are certain you no longer need the pre-existing workflow file ## Enabling the default setup takes too long -If enabling your default setup is taking too long, try canceling the workflow run and restarting the setup. To restart your setup, navigate to the main page of your repository, then click {% octicon "play" aria-label="The play icon" %} **Actions**. Click the **{% data variables.product.prodname_codeql %}** workflow run that's in progress, then click **Cancel workflow**. Once {% octicon "stop" aria-label="The stop icon" %} appears beside the workflow run name, navigate back to the **Code security and analysis** settings and re-enable the default setup. If the default setup continues to stall, please contact {% data variables.contact.contact_support %} or try enabling the advanced setup. For more information, see "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning-for-a-repository#creating-an-advanced-setup)." +If enabling your default setup is taking too long, try canceling the workflow run and restarting the setup. To restart your setup, navigate to the main page of your repository, then click {% octicon "play" aria-hidden="true" %} **Actions**. Click the **{% data variables.product.prodname_codeql %}** workflow run that's in progress, then click **Cancel workflow**. Once {% octicon "stop" aria-label="The stop icon" %} appears beside the workflow run name, navigate back to the **Code security and analysis** settings and re-enable the default setup. If the default setup continues to stall, please contact {% data variables.contact.contact_support %} or try enabling the advanced setup. For more information, see "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning-for-a-repository#creating-an-advanced-setup)." ## Unclear what triggered a workflow run diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md index 271667f961..07652c1aea 100644 --- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md +++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md @@ -78,7 +78,6 @@ After configuring {% data variables.product.prodname_code_scanning %} for your r 1. Review the logging output from the actions in this workflow as they run. -1. Optionally, to see more detail about the commit that triggered the workflow run, click {% octicon "git-commit" aria-label="The commit icon" %} **SHORT COMMIT HASH**. This short commit hash is 7 lowercase characters immediately following the commit author's username. +1. Optionally, to see more detail about the commit that triggered the workflow run, click the short commit hash. The short commit hash is 7 lowercase characters immediately following the commit author's username. 1. Once all jobs are complete, you can view the details of any {% data variables.product.prodname_code_scanning %} alerts that were identified. For more information, see "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." - diff --git a/content/code-security/getting-started/securing-your-repository.md b/content/code-security/getting-started/securing-your-repository.md index 1e7819f658..d90ee97b39 100644 --- a/content/code-security/getting-started/securing-your-repository.md +++ b/content/code-security/getting-started/securing-your-repository.md @@ -111,8 +111,8 @@ You can configure {% data variables.product.prodname_code_scanning %} to automat {% ifversion code-scanning-without-workflow %} -1. From the main page of your repository, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. -1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Code security and analysis**. +1. From the main page of your repository, click {% octicon "gear" aria-hidden="true" %} **Settings**. +1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-hidden="true" %} Code security and analysis**. 1. In the "{% data variables.product.prodname_code_scanning_caps %}" section, select **Set up** {% octicon "triangle-down" aria-label="The downwards-facing triangle icon" %}, then click **Default**. 1. In the pop-up window that appears, review the default configuration settings for your repository, then click **Enable {% data variables.product.prodname_codeql %}**. diff --git a/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md b/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md index 796f434570..e513b9a911 100644 --- a/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md +++ b/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md @@ -77,7 +77,7 @@ shortTitle: Manage secret alerts {% endnote %} -In the view for an active {% data variables.product.company_short %} token alert, you can review certain metadata about the token. This metadata may help you identify the token and decide what remediation steps to take. For more information on viewing individual alerts, see "[Managing {% data variables.product.prodname_secret_scanning %} alerts](#managing-secret-scanning-alerts)." +In the view for an active {% data variables.product.company_short %} token alert, you can review certain metadata about the token. This metadata may help you identify the token and decide what remediation steps to take. For more information on viewing individual alerts, see "[Managing {% data variables.product.prodname_secret_scanning %} alerts](#managing-secret-scanning-alerts)." Tokens, like {% data variables.product.pat_generic %} and other credentials, are considered personal information. For more information about using {% data variables.product.company_short %} tokens, see [GitHub's Privacy Statement](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement) and [Acceptable Use Policies](/free-pro-team@latest/site-policy/acceptable-use-policies/github-acceptable-use-policies). @@ -120,7 +120,7 @@ Once a secret has been committed to a repository, you should consider the secret {% ifversion secret-scanning-notification-settings %} {% data reusables.repositories.navigate-to-repo %} -1. To start watching the repository, select **{% octicon "eye" aria-label="The Eye icon" %}Watch**. +1. To start watching the repository, select **{% octicon "eye" aria-hidden="true" %} Watch**. ![Screenshot of the repository's main page. A dropdown menu, titled "Watch", is highlighted with an orange outline.](/assets/images/help/repository/repository-watch-dropdown.png) diff --git a/content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md b/content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md index 8e4ddc7820..fb3eb30e5a 100644 --- a/content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md +++ b/content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md @@ -80,7 +80,7 @@ You may have a codespace that you want to keep for longer than the retention per Codespaces incur storage costs, or consume your included storage allowance if the codespace is owned by your personal {% data variables.product.prodname_dotcom %} account. You should therefore be aware of the cost implications of storing codespaces indefinitely. For more information, see "[AUTOTITLE](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#about-billing-for-storage-usage)." {% data reusables.codespaces.your-codespaces-procedure-step %} -1. To the right of the codespace you want to exempt from automatic deletion, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "bookmark" aria-label="The bookmark icon" %} Keep codespace**. +1. To the right of the codespace you want to exempt from automatic deletion, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "bookmark" aria-hidden="true" %} Keep codespace**. ![Screenshot of the dropdown menu for an active codespace. The "Keep codespace" option has a tooltip saying "Expires 10 days after shutdown."](/assets/images/help/codespaces/keep-codespace.png) diff --git a/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md b/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md index 28e5de6930..0c2900b2ef 100644 --- a/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md +++ b/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md @@ -74,7 +74,7 @@ If you want to use Git hooks for your codespace, then you should set up hooks us ![Screenshot of the expanded branch dropdown menu, listing various branches. The dropdown menu, labeled with a branch icon and "trunk," is highlighted with a dark orange outline.](/assets/images/help/codespaces/branch-drop-down.png) -1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab. +1. Click the **{% octicon "code" aria-hidden="true" %} Code** button, then click the **Codespaces** tab. If codespaces for this repository are billable to an organization, or its parent enterprise, a message is displayed below the **Create codespace on BRANCH** button telling you who will pay for the codespace. @@ -114,16 +114,16 @@ If you want to use Git hooks for your codespace, then you should set up hooks us ## Recommended secrets -The names of user-defined secrets may be displayed on the advanced options page when you create a codespace. This will happen if recommended secrets have been specified in the dev container configuration you have selected. - +The names of user-defined secrets may be displayed on the advanced options page when you create a codespace. This will happen if recommended secrets have been specified in the dev container configuration you have selected. + Screenshot of the "Create codespace" page with four recommended secrets highlighted with a dark orange outline. Entering values for these secrets, when you're prompted to do so, is recommended because it's likely your project will need values for these secrets. However, supplying values is not required for you to create a codespace. You can set these secrets within the codespace if you prefer. If you enter a value for a recommended secret, the secret will available in the new codespace. When you click **Create codespace**, the secret is also added to your personal settings for {% data variables.product.prodname_codespaces %}, so you will not need to enter a value for the secret in future when you create a codespace for this repository. - + If the name of a secret is shown with a checkbox that is unavailable for selection, and no input box, this is because you already have a secret of this name configured in your personal settings for {% data variables.product.prodname_codespaces %}, and you have associated it with this repository. If you've created a secret of this name but have not associated it with this repository, the checkbox will be available to select and by doing so you can update your settings to add the association. - + If you want to change the value of a preselected secret you can do so from your personal settings for {% data variables.product.prodname_codespaces %} at [github.com/settings/codespaces](https://github.com/settings/codespaces). For more information, see "[AUTOTITLE](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)." {% endwebui %} diff --git a/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md b/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md index 1780fe7aa0..71d0c768c6 100644 --- a/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md +++ b/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md @@ -63,7 +63,7 @@ You can create a codespace from any template repository, then publish your work {% note %} - **Note:** If you're a maintainer of the template repository, and want to commit changes to the template repository itself, you should create a codespace from the **{% octicon "code" aria-label="The code icon" %} Code** dropdown. For more information, see "[AUTOTITLE](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." + **Note:** If you're a maintainer of the template repository, and want to commit changes to the template repository itself, you should create a codespace from the **{% octicon "code" aria-hidden="true" %} Code** dropdown. For more information, see "[AUTOTITLE](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." {% endnote %} diff --git a/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/content/codespaces/developing-in-codespaces/deleting-a-codespace.md index 1a58d4b093..197da20cf9 100644 --- a/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ b/content/codespaces/developing-in-codespaces/deleting-a-codespace.md @@ -43,7 +43,7 @@ There are costs associated with storing codespaces. You should therefore delete {% webui %} {% data reusables.codespaces.your-codespaces-procedure-step %} -1. To the right of the codespace you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "trash" aria-label="The trash icon" %} Delete**. +1. To the right of the codespace you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "trash" aria-hidden="true" %} Delete**. ![Screenshot of a list of codespaces with the dropdown menu for one of them displayed, showing the "Delete" option.](/assets/images/help/codespaces/delete-codespace.png) diff --git a/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md b/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md index c596aead12..b4a65ff8cd 100644 --- a/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md +++ b/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md @@ -27,7 +27,7 @@ redirect_from: {% data reusables.repositories.sidebar-pr %} 1. In the list of pull requests, click the pull request you'd like to open in {% data variables.product.prodname_codespaces %}. -1. On the right-hand side of your screen, click **{% octicon "code" aria-label="The code icon" %} Code**. +1. On the right-hand side of your screen, click **{% octicon "code" aria-hidden="true" %} Code**. 1. In the {% data variables.product.prodname_codespaces %} tab, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}) ![Screenshot of the "Code" dropdown with the "{% data variables.product.prodname_codespaces %}" tab selected. The message "No codespaces" is displayed. The plus button is highlighted.](/assets/images/help/codespaces/open-with-codespaces-pr.png) @@ -67,4 +67,4 @@ For more information on reviewing a pull request, see "[AUTOTITLE](/pull-request ## View comments from a review in {% data variables.product.prodname_codespaces %} -Once you have received feedback on a pull request, you can [open it in a codespace](#opening-a-pull-request-in-codespaces) in your web browser, or in {% data variables.product.prodname_vscode_shortname %}, to see the [review comments](#reviewing-a-pull-request-in-codespaces). From there you can respond to comments, add reactions, or dismiss the review. +Once you have received feedback on a pull request, you can [open it in a codespace](#opening-a-pull-request-in-codespaces) in your web browser, or in {% data variables.product.prodname_vscode_shortname %}, to see the [review comments](#reviewing-a-pull-request-in-codespaces). From there you can respond to comments, add reactions, or dismiss the review. diff --git a/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md b/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md index b9b16a44a2..a0f32e5642 100644 --- a/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md +++ b/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md @@ -20,7 +20,7 @@ If it currently takes more than 2 minutes to create a codespace for a repository By default, whenever you push changes to your repository, {% data variables.product.prodname_github_codespaces %} uses {% data variables.product.prodname_actions %} to automatically update your prebuilds. -When prebuilds are available for a particular branch of a repository, a particular dev container configuration file, and for your region, you'll see the "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" label in the list of machine type options when you create a codespace. If a prebuild is still being created, you will see the "{% octicon "history" aria-label="The history icon" %} Prebuild in progress" label. For more information, see "[AUTOTITLE](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." +When prebuilds are available for a particular branch of a repository, a particular dev container configuration file, and for your region, you'll see the "{% octicon "zap" aria-hidden="true" %} Prebuild ready" label in the list of machine type options when you create a codespace. If a prebuild is still being created, you will see the "{% octicon "history" aria-hidden="true" %} Prebuild in progress" label. For more information, see "[AUTOTITLE](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." ![Screenshot of a list of available machine types: 2, 4, 8, 16, and 32 core, all labeled "Prebuild ready."](/assets/images/help/codespaces/choose-custom-machine-type.png) diff --git a/content/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers.md b/content/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers.md index 4caea464f5..b3940ee789 100644 --- a/content/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers.md +++ b/content/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers.md @@ -181,7 +181,7 @@ If none of the predefined configurations meets your needs, you can create a cust ### Adding a `devcontainer.json` file If you don't already have a `devcontainer.json` file in your repository, you can quickly add one from {% data variables.product.prodname_dotcom_the_website %}. -1. Navigate to your repository and click the **{% octicon "code" aria-label="The code icon" %} Code** dropdown. +1. Navigate to your repository and click the **{% octicon "code" aria-hidden="true" %} Code** dropdown. 1. In the **Codespaces** tab, click the ellipsis (**...**), then select **Configure dev container**. ![Screenshot of the "Code" dropdown, and, within it, another dropdown with the "Configure dev container" option highlighted.](/assets/images/help/codespaces/configure-dev-container.png) diff --git a/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-repository/facilitating-quick-creation-and-resumption-of-codespaces.md b/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-repository/facilitating-quick-creation-and-resumption-of-codespaces.md index 937c5b2095..3b0297859c 100644 --- a/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-repository/facilitating-quick-creation-and-resumption-of-codespaces.md +++ b/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-repository/facilitating-quick-creation-and-resumption-of-codespaces.md @@ -45,7 +45,7 @@ You can use the "Share a deep link" option to configure more options for the cod ![Screenshot of the expanded branch dropdown menu, listing various branches. The dropdown menu, labeled with a branch icon and "trunk," is highlighted with a dark orange outline.](/assets/images/help/codespaces/branch-drop-down.png) -1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab. +1. Click the **{% octicon "code" aria-hidden="true" %} Code** button, then click the **Codespaces** tab. 1. To open the "Share codespace configuration" window, at the top right of the **Codespaces** tab, select {% octicon "kebab-horizontal" aria-label="Codespace repository configuration" %}, then click **Share a deep link**. ![Screenshot of the options dropdown in the "{% data variables.product.prodname_codespaces %}" tab. The "Share a deep link" option is highlighted with an orange outline.](/assets/images/help/codespaces/share-deep-link.png) @@ -60,7 +60,7 @@ You can use the "Share a deep link" option to configure more options for the cod You can create a link to a page for resuming your most recent codespace that matches the repository, branch, and other options specified in the URL. -Add `?quickstart=1` to a `codespaces.new` URL, such as the URLs listed in the previous section of this article. This produces a URL that displays a "Resume codespace" page. +Add `?quickstart=1` to a `codespaces.new` URL, such as the URLs listed in the previous section of this article. This produces a URL that displays a "Resume codespace" page. For example, the URL `https://codespaces.new/octo-org/octo-repo?quickstart=1` opens a page to allow you to resume your most recent codespace for the default branch of the `octo-org/octo-repo` repository. @@ -68,7 +68,7 @@ For example, the URL `https://codespaces.new/octo-org/octo-repo?quickstart=1` op {% note %} -**Notes**: +**Notes**: - If the `codespaces.new` URL already contains a query string, add `&quickstart=1` at the end of the query string. - This type of URL will always open a codespace in the {% data variables.product.prodname_vscode_shortname %} web client, even if this is not set as your default editor for {% data variables.product.prodname_github_codespaces %}. @@ -101,5 +101,5 @@ This type of URL is useful, for instance, in a README for your repository as it ``` The example Markdown is rendered like this: - + [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/github/docs) \ No newline at end of file diff --git a/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md b/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md index f1f0cb25a9..600555f804 100644 --- a/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md +++ b/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md @@ -12,7 +12,7 @@ shortTitle: Exporting changes ## About exporting changes -While using {% data variables.product.prodname_github_codespaces %}, you may want to export your changes to a branch without launching your codespace. This can be useful when you have hit a [spending limit](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces) or have a general issue accessing your codespace. +While using {% data variables.product.prodname_github_codespaces %}, you may want to export your changes to a branch without launching your codespace. This can be useful when you have hit a [spending limit](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces) or have a general issue accessing your codespace. You can export your changes in one of several ways, depending on how you created the codespace. In every case, only the Git branch that is currently checked out in the codespace is exported. Work contained in other branches is not exported. @@ -24,7 +24,7 @@ You can export your changes in one of several ways, depending on how you created The following steps describe how to export your changes to a branch or fork. For information on exporting an unpublished codespace to a new repository, see "[AUTOTITLE](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template#publishing-from-githubcom)." -{% data reusables.codespaces.your-codespaces-procedure-step %} Or, for an individual repository, click the **{% octicon "code" aria-label="The code icon" %} Code** menu. +{% data reusables.codespaces.your-codespaces-procedure-step %} Or, for an individual repository, click the **{% octicon "code" aria-hidden="true" %} Code** menu. 1. Click the ellipsis (**...**) to the right of the codespace you want to export from. 1. Select **{% octicon "git-branch" aria-hidden="true" %} Export changes to a branch** or **{% octicon "git-branch" aria-hidden="true" %} Export changes to a fork**. diff --git a/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/content/codespaces/troubleshooting/troubleshooting-prebuilds.md index 98171c7103..8d366dcea2 100644 --- a/content/codespaces/troubleshooting/troubleshooting-prebuilds.md +++ b/content/codespaces/troubleshooting/troubleshooting-prebuilds.md @@ -14,7 +14,7 @@ For more information about {% data variables.product.prodname_github_codespaces ## Checking whether a codespace was created from a prebuild? -When you create a codespace, you can choose the type of the virtual machine you want to use. If a prebuild is available for the type of virtual machine, "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" is shown next to it. +When you create a codespace, you can choose the type of the virtual machine you want to use. If a prebuild is available for the type of virtual machine, "{% octicon "zap" aria-hidden="true" %} Prebuild ready" is shown next to it. ![Screenshot of a list of available machine types: 2, 4, 8, 16, and 32 core, all labeled "Prebuild ready."](/assets/images/help/codespaces/choose-custom-machine-type.png) @@ -46,18 +46,18 @@ You can check how much storage space has been consumed by prebuilds in your curr ## The "Prebuild Ready" label is sometimes missing -You may notice that sometimes, when you create a new codespace from a prebuild-enabled branch, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed in the dialog box for choosing a machine type. This means that prebuilds are not currently available. +You may notice that sometimes, when you create a new codespace from a prebuild-enabled branch, the "{% octicon "zap" aria-hidden="true" %} Prebuild Ready" label is not displayed in the dialog box for choosing a machine type. This means that prebuilds are not currently available. -By default, each time you push to a prebuild-enabled branch, the prebuild is updated. If the push involves a change to the dev container configuration then, while the update is in progress, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is removed from the list of machine types. During this time you can still create codespaces without a prebuild. If required, you can reduce the occasions on which prebuilds are unavailable for a repository by setting the prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. For more information, see "[AUTOTITLE](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)." +By default, each time you push to a prebuild-enabled branch, the prebuild is updated. If the push involves a change to the dev container configuration then, while the update is in progress, the "{% octicon "zap" aria-hidden="true" %} Prebuild Ready" label is removed from the list of machine types. During this time you can still create codespaces without a prebuild. If required, you can reduce the occasions on which prebuilds are unavailable for a repository by setting the prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. For more information, see "[AUTOTITLE](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)." If your branch is not specifically enabled for prebuilds it may still benefit from prebuilds if it was branched from a prebuild-enabled branch. However, if the dev container configuration is changed on your branch, so that it's not the same as the configuration on the base branch, prebuilds will no longer be available on your branch. -Here are things to check if the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed for a particular branch: +Here are things to check if the "{% octicon "zap" aaria-hidden="true" %} Prebuild Ready" label is not displayed for a particular branch: * Confirm that a prebuild configuration exists for this branch. If you’re not a repository administrator, you'll need to reach out to one to confirm this. * Confirm that the prebuild configuration includes your region. * Check whether a change to the dev container configuration was pushed to the prebuild-enabled branch recently. If so, you will typically have to wait until the prebuild workflow run for this push completes before prebuilds are available again. -* If no configuration changes were recently made, go to the **Actions** tab of your repository, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} Prebuilds** in the workflows list, and check that prebuild workflow runs for the branch are succeeding. If latest runs of a workflow failed, and one or more of these failed runs contained changes to the dev container configuration, then there will be no available prebuilds for the associated branch. +* If no configuration changes were recently made, go to the **Actions** tab of your repository, click **{% octicon "codespaces" aria-hidden="true" %} {% data variables.product.prodname_codespaces %} Prebuilds** in the workflows list, and check that prebuild workflow runs for the branch are succeeding. If latest runs of a workflow failed, and one or more of these failed runs contained changes to the dev container configuration, then there will be no available prebuilds for the associated branch. ## Some resources cannot be accessed in codespaces created using a prebuild diff --git a/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-in-your-organization.md b/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-in-your-organization.md index 5f48470ba2..9cdf969e75 100644 --- a/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-in-your-organization.md +++ b/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-in-your-organization.md @@ -27,7 +27,7 @@ Depending on the policy settings configured at the enterprise level, an organiza {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-label="The copilot icon" %} {% data variables.product.prodname_copilot_short %}**, and then click **Access**. +1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**, and then click **Access**. 1. Under "User permissions," to enable {% data variables.product.prodname_copilot %} for all current and future users in your organization, select **Purchase for all members**. 1. In the "Confirm seat assignment" dialog, to confirm that you want to enable {% data variables.product.prodname_copilot %} for all current and future users in your organization, click **Confirm**. 1. To save your changes, click **Save**. diff --git a/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/syncing-your-branch-in-github-desktop.md b/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/syncing-your-branch-in-github-desktop.md index 3252f7fffe..ddc2062355 100644 --- a/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/syncing-your-branch-in-github-desktop.md +++ b/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/syncing-your-branch-in-github-desktop.md @@ -21,7 +21,7 @@ Some workflows require or benefit from rebasing instead of merging. By rebasing ## Pulling to your local branch from the remote -1. In {% data variables.product.prodname_desktop %}, use the {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch** drop-down, and select the local branch you want to update. +1. In {% data variables.product.prodname_desktop %}, use the {% octicon "git-branch" aria-hidden="true" %} **Current Branch** drop-down, and select the local branch you want to update. 2. To check for commits on the remote branch, click **Fetch origin** ![Screenshot of the repository bar. The "Fetch origin" button, displayed with an icon of two arrows forming a circle, is outlined in orange.](/assets/images/help/desktop/fetch-button.png) diff --git a/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project-in-github-desktop.md b/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project-in-github-desktop.md index 207fa69eb3..c03c871684 100644 --- a/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project-in-github-desktop.md +++ b/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project-in-github-desktop.md @@ -17,7 +17,7 @@ shortTitle: Commit & review changes ## Choosing a branch and making changes -1. [Create a new branch](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches-in-github-desktop), or select an existing branch by clicking {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch** on the toolbar and selecting the branch from the list. +1. [Create a new branch](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches-in-github-desktop), or select an existing branch by clicking {% octicon "git-branch" aria-hidden="true" %} **Current Branch** on the toolbar and selecting the branch from the list. ![Screenshot of the "Current Branch" dropdown view. Under "Recent Branches", a branch, named "my-feature", is highlighted with an orange outline.](/assets/images/help/desktop/select-branch-from-dropdown.png) {% data reusables.desktop.make-changes %} @@ -118,7 +118,6 @@ Once you're satisfied with the changes you've chosen to include in your commit, 6. If you have a pull request based off the branch you are working on, {% data variables.product.prodname_desktop %} will display the status of the checks that have run for the pull request next to the "Current Branch" section of the repository bar. For more information about checks, see "[AUTOTITLE](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." - If a pull request has not been created for the current branch, {% data variables.product.prodname_desktop %} will give you the option to preview the changes and create one. For more information, see "[AUTOTITLE](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request-from-github-desktop)." ![Screenshot of the "No local changes" view. A button, labeled "Preview Pull Request", is highlighted with an orange outline.](/assets/images/help/desktop/mac-preview-pull-request.png) diff --git a/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches-in-github-desktop.md b/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches-in-github-desktop.md index f6866f23d9..c3ce170f41 100644 --- a/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches-in-github-desktop.md +++ b/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches-in-github-desktop.md @@ -59,7 +59,7 @@ You can always create a branch in {% data variables.product.prodname_desktop %} If you create a branch on {% data variables.product.product_name %}, you'll need to publish the branch to make it available for collaboration on {% data variables.product.prodname_dotcom %}. -1. In the repository bar, click {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch**, then click the branch that you want to publish. +1. In the repository bar, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch**, then click the branch that you want to publish. ![Screenshot of the "Current Branch" dropdown view. Under "Recent Branches", a branch, named "my-feature", is highlighted with an orange outline.](/assets/images/help/desktop/select-branch-from-dropdown.png) 2. Click **Publish branch**. ![Screenshot of the repository bar. On the right-hand side, a button, labeled "Publish branch", is highlighted with an orange outline.](/assets/images/help/desktop/publish-branch-button.png) @@ -73,7 +73,7 @@ You can view and make commits to any of your repository's branches. If you have {% endtip %} -1. In the repository bar, click {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch**, then click the branch that you want to switch to. +1. In the repository bar, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch**, then click the branch that you want to switch to. ![Screenshot of the "Current Branch" dropdown view. Under "Recent Branches", a branch, named "my-feature", is highlighted with an orange outline.](/assets/images/help/desktop/select-branch-from-dropdown.png) 1. If you have saved, uncommitted changes, in the "Switch Branch" window, select **Leave my changes on CURRENT-BRANCH** or **Bring my changes to NEW-BRANCH**, then click **Switch Branch**. diff --git a/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/cherry-picking-a-commit-in-github-desktop.md b/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/cherry-picking-a-commit-in-github-desktop.md index 50458d7503..fb47ae01ff 100644 --- a/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/cherry-picking-a-commit-in-github-desktop.md +++ b/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/cherry-picking-a-commit-in-github-desktop.md @@ -22,7 +22,7 @@ You can also use cherry-picking when collaborating with a team. Some projects in ![Screenshot of the "Current Branch" dropdown view. Under "Recent Branches", a branch, named "my-feature", is highlighted with an orange outline.](/assets/images/help/desktop/select-branch-from-dropdown.png) {% data reusables.desktop.history-tab %} -4. Drag the commit that you want to cherry-pick from the "History" tab to the {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch** dropdown menu, then drop the commit on the branch that you want to copy the commit to. +4. Drag the commit that you want to cherry-pick from the "History" tab to the {% octicon "git-branch" aria-hidden="true" %} **Current Branch** dropdown menu, then drop the commit on the branch that you want to copy the commit to. ![Screenshot of the "History" tab and the "Current Branch" dropdown view. The cursor hovers over the "my-feature" branch, and "plus one" icons indicate the addition of one commit.](/assets/images/help/desktop/cherry-picking.png) diff --git a/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md b/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md index bd6a4b6832..1e223571fe 100644 --- a/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md +++ b/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md @@ -20,7 +20,7 @@ versions: 4. Click on the pull request number, to the right of the pull request branch name. ![Screenshot of the repository bar. Next to the "Current Branch" button, a numbered label, displayed with a red cross for failing checks, is outlined in orange.](/assets/images/help/desktop/checks-dialog.png) -5. To re-run failed checks, click **{% octicon "sync" aria-label="The sync icon" %} Re-run** and select **Re-run Failed Checks**. +5. To re-run failed checks, click **{% octicon "sync" aria-hidden="true" %} Re-run** and select **Re-run Failed Checks**. ![Screenshot of a dropdown view from a pull request label. Next to the message "Some checks were not successful", a button labeled "Re-run" is outlined in orange.](/assets/images/help/desktop/re-run-failed-checks.png) 6. To re-run individual checks, hover over the individual check you want to re-run and select the {% octicon "sync" aria-label="The sync icon" %} icon to re-run the check. diff --git a/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/content/discussions/managing-discussions-for-your-community/managing-discussions.md index 3fb0068fb9..d9a338d6b6 100644 --- a/content/discussions/managing-discussions-for-your-community/managing-discussions.md +++ b/content/discussions/managing-discussions-for-your-community/managing-discussions.md @@ -62,7 +62,7 @@ You can pin up to four important discussions above the list of discussions for t {% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**. +1. In the right sidebar, click {% octicon "pin" aria-hidden="true" %} **Pin discussion**. {% ifversion discussions-category-specific-pins %} ![Screenshot of the right sidebar of a discussion. The "Pin discussion" option is highlighted with an orange outline.](/assets/images/help/discussions/click-pin-discussion-with-category-pins.png){% else %} @@ -80,7 +80,7 @@ You can pin up to four important discussions above the list of discussions in a {% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion to CATEGORY**. +1. In the right sidebar, click {% octicon "pin" aria-hidden="true" %} **Pin discussion to CATEGORY**. ![Screenshot of the right sidebar of a discussion. The "Pin discussion to Q&A" option is outlined in dark orange.](/assets/images/help/discussions/pin-discussion-to-category.png) @@ -94,7 +94,7 @@ Editing a pinned discussion will not change the discussion's category. For more {% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**. {% ifversion discussions-category-specific-pins %} +1. In the right sidebar, click {% octicon "pencil" aria-hidden="true" %} **Edit pinned discussion**. {% ifversion discussions-category-specific-pins %} ![Screenshot of the right sidebar of a discussion. The "Edit pinned discussion" option is outlined in dark orange.](/assets/images/help/discussions/edit-pinned-discussion-with-category-pins.png){% endif %} 1. Customize the look of the pinned discussion. @@ -114,7 +114,7 @@ You can unpin a globally pinned discussion. This will not delete the discussion, {% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**. +1. In the right sidebar, click {% octicon "pin" aria-hidden="true" %} **Unpin discussion**. ![Screenshot of the "Unpin discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-unpin-discussion.png) @@ -128,7 +128,7 @@ You can unpin a discussion pinned to a specific category. This will not delete t {% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion from this category**. +1. In the right sidebar, click {% octicon "pin" aria-hidden="true" %} **Unpin discussion from this category**. ![Screenshot of the right sidebar of a discussion. The "Unpin discussion from this category" option is outlined in dark orange.](/assets/images/help/discussions/unpin-discussion-from-category.png) @@ -142,7 +142,7 @@ To transfer a discussion, you must have permissions to create discussions in the {% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %}**Transfer this discussion**{% else %}**Transfer discussion**{% endif %}. +1. In the right sidebar, click {% octicon "arrow-right" aria-hidden="true" %} {% ifversion discussions-category-specific-pins %}**Transfer this discussion**{% else %}**Transfer discussion**{% endif %}. {% ifversion discussions-category-specific-pins %} ![Screenshot of the right sidebar of a discussion. The "Transfer this discussion" option is outlined in dark orange.](/assets/images/help/discussions/transfer-discussion-with-category-pin.png) {% else %} @@ -157,7 +157,7 @@ To transfer a discussion, you must have permissions to create discussions in the {% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**. +1. In the right sidebar, click {% octicon "trash" aria-hidden="true" %} **Delete discussion**. {% ifversion discussions-category-specific-pins %} ![Screenshot of the right sidebar of a discussion. The "Delete discussion" option is outlined in dark orange.](/assets/images/help/discussions/delete-discussion-with-category-pins.png){% endif %} diff --git a/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md b/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md index ae6c17c6b8..41e2318a16 100644 --- a/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md +++ b/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md @@ -30,7 +30,7 @@ You can star repositories listed in the {% data variables.product.prodname_commu Repository listings in the {% data variables.product.prodname_community_exchange %} gallery can be sorted on the number of stars a repository has. -To star a repository: Go to your {% data variables.product.prodname_community_exchange %} home page, find the repository you want to star, and click {% octicon "star" aria-label="The star icon" %} **Star** button found right by its name. +To star a repository: Go to your {% data variables.product.prodname_community_exchange %} home page, find the repository you want to star, and click {% octicon "star" aria-hidden="true" %} **Star** button found right by its name. ## Reporting abuse diff --git a/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md b/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md index 4df808e5af..89ac6b0c1d 100644 --- a/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md +++ b/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md @@ -78,7 +78,7 @@ If you use a template repository for an assignment, you can define a dev contain When a student opens an assignment, the repository's README file includes their teacher's recommendation of the IDE they should use for the work. -Students can launch a new or existing codespace by clicking the **Open in GitHub Codespace** button in the README, or by clicking the **{% octicon "code" aria-label="The code icon" %} Code** button on the main page of the assignment repository, then selecting the **Codespaces** tab. From the **Codespaces** tab you can select an existing codespace or create a new one. For more information, see "[AUTOTITLE](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." +Students can launch a new or existing codespace by clicking the **Open in GitHub Codespace** button in the README, or by clicking the **{% octicon "code" aria-hidden="true" %} Code** button on the main page of the assignment repository, then selecting the **Codespaces** tab. From the **Codespaces** tab you can select an existing codespace or create a new one. For more information, see "[AUTOTITLE](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." ![Screenshot of the assignment repository. The "Code" dropdown menu to launch a new codespace is expanded.](/assets/images/help/classroom/student-launch-new-codespace.png) diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/editing-an-assignment.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/editing-an-assignment.md index 8d9ef322c0..ba0ec6befe 100644 --- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/editing-an-assignment.md +++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/editing-an-assignment.md @@ -14,7 +14,7 @@ After creating an assignment, you can edit many aspects of the assignment to bet {% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} -1. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, next to the assignment you would like to edit, click {% octicon "pencil" aria-label="The pencil icon" %}. +1. In the {% octicon "repo" aria-hidden="true" %} **Assignments** tab, next to the assignment you would like to edit, click {% octicon "pencil" aria-label="The pencil icon" %}. {% note %} diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md index 2350f97111..a3b2d96172 100644 --- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md +++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md @@ -17,7 +17,7 @@ The copied assignment includes assignment details such as the name, source repos 1. Sign into {% data variables.product.prodname_classroom_with_url %}. 1. Navigate to the classroom that has the assignment that you want to reuse. 1. In the list of assignments, click the assignment you want to reuse. -1. Select the **{% octicon "pencil" aria-label="The pencil icon" %} Edit** dropdown menu in the top right of the page, then click **{% octicon "sync" aria-label="The sync icon" %} Reuse assignment**. +1. Select the **{% octicon "pencil" aria-hidden="true" %} Edit** dropdown menu in the top right of the page, then click **{% octicon "sync" aria-hidden="true" %} Reuse assignment**. ![Screenshot of an assignment. The "Edit" dropdown is expanded and the "Reuse assignment" option is outlined in dark orange.](/assets/images/help/classroom/reuse-assignment-button.png) diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md index db7b417ff3..1c13c2416b 100644 --- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md +++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md @@ -27,7 +27,7 @@ The Git & {% data variables.product.company_short %} starter assignment is a pre 1. Sign into {% data variables.product.prodname_classroom_with_url %}. 1. Navigate to a classroom. -1. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click the link in the blue banner. +1. In the {% octicon "repo" aria-hidden="true" %} **Assignments** tab, click the link in the blue banner. ## Setting up the basics for an assignment diff --git a/content/get-started/using-github/github-mobile.md b/content/get-started/using-github/github-mobile.md index c8554f90f5..5c3ce3fe42 100644 --- a/content/get-started/using-github/github-mobile.md +++ b/content/get-started/using-github/github-mobile.md @@ -55,11 +55,11 @@ During the beta for {% data variables.product.prodname_mobile %} with {% data va ### Adding, switching, or signing out of accounts -You can sign into mobile with a personal account on {% data variables.product.prodname_ghe_server %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in. +You can sign into mobile with a personal account on {% data variables.product.prodname_ghe_server %}. At the bottom of the app, long-press {% octicon "person" aria-hidden="true" %} **Profile**, then tap {% octicon "plus" aria-hidden="true" %} **Add Enterprise Account**. Follow the prompts to sign in. -After you sign into mobile with a personal account on {% data variables.product.prodname_ghe_server %}, you can switch between the account and your account on {% data variables.product.prodname_dotcom_the_website %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to. +After you sign into mobile with a personal account on {% data variables.product.prodname_ghe_server %}, you can switch between the account and your account on {% data variables.product.prodname_dotcom_the_website %}. At the bottom of the app, long-press {% octicon "person" aria-hidden="true" %} **Profile**, then tap the account you want to switch to. -If you no longer need to access data for your personal account on {% data variables.product.prodname_ghe_server %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**. +If you no longer need to access data for your personal account on {% data variables.product.prodname_ghe_server %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-hidden="true" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**. ## Supported languages for {% data variables.product.prodname_mobile %} diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet.md b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet.md index 89c3c7f184..b10afeb5f1 100644 --- a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet.md +++ b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet.md @@ -31,7 +31,7 @@ This type of permanent link will render as a code snippet only in the repository {% data reusables.repositories.navigate-to-repo %} 1. Locate the code you'd like to link to: - To link to code from a file, navigate to the file. - - To link to code from a pull request, navigate to the pull request and click {% octicon "diff" aria-label="The file diff icon" %} **Files changed**. Then, browse to the file that contains the code you want include in your comment, and click **View**. + - To link to code from a pull request, navigate to the pull request and click {% octicon "diff" aria-hidden="true" %} **Files changed**. Then, browse to the file that contains the code you want include in your comment, and click **View**. {% data reusables.repositories.choose-line-or-range %} 1. To the left of the line or range of lines, click {% octicon "kebab-horizontal" aria-label="Code line X options" %}. In the drop-down menu, click **Copy permalink**. diff --git a/content/graphql/overview/public-schema.md b/content/graphql/overview/public-schema.md index 131d11661d..4e498ea4fd 100644 --- a/content/graphql/overview/public-schema.md +++ b/content/graphql/overview/public-schema.md @@ -18,18 +18,18 @@ Alternatively, you can download the latest version of the public schema here: {% ifversion fpt or ghec %} -[{% octicon "desktop-download" aria-label="The desktop download icon" %} `schema.docs.graphql`](/public/schema.docs.graphql) +[{% octicon "desktop-download" aria-label="Download" %} `schema.docs.graphql`](/public/schema.docs.graphql) {% endif %} {% ifversion ghes %} -[{% octicon "desktop-download" aria-label="The desktop download icon" %} `schema.docs-enterprise.graphql`](/public/ghes-{{ allVersions[currentVersion].currentRelease }}/schema.docs-enterprise.graphql) ({{ allVersions[currentVersion].versionTitle }}) +[{% octicon "desktop-download" aria-label="Download" %} `schema.docs-enterprise.graphql`](/public/ghes-{{ allVersions[currentVersion].currentRelease }}/schema.docs-enterprise.graphql) ({{ allVersions[currentVersion].versionTitle }}) {% endif %} {% ifversion ghae %} -[{% octicon "desktop-download" aria-label="The desktop download icon" %} `schema.docs-ghae.graphql`](/public/ghae/schema.docs-ghae.graphql) ({{ allVersions[currentVersion].versionTitle }}) +[{% octicon "desktop-download" aria-label="Download" %} `schema.docs-ghae.graphql`](/public/ghae/schema.docs-ghae.graphql) ({{ allVersions[currentVersion].versionTitle }}) {% endif %} diff --git a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md index fef1f1586f..7eb8d07916 100644 --- a/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md +++ b/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md @@ -38,7 +38,7 @@ You can also configure workflow automations to keep your {% data variables.proje 1. On the top of your profile page, in the main navigation, click {% octicon "project" aria-hidden="true" %} **Projects**. ![Screenshot showing profile tabs. The 'Projects' tab is highlighted with an orange outline.](/assets/images/help/projects-v2/tab-projects.png){% ifversion projects-v2 %} - + 1. Click **Projects (classic)**{% endif %} {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} diff --git a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md index 5a86b418cf..640edf8e13 100644 --- a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md +++ b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md @@ -35,7 +35,7 @@ You can put a maximum of 2,500 cards into each project column. If a column has r ## Adding issues and pull requests to a {% data variables.projects.projects_v1_board %} 1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to add issues and pull requests. -2. In your {% data variables.projects.projects_v1_board %}, click {% octicon "plus" aria-label="The plus icon" %} **Add cards**. +2. In your {% data variables.projects.projects_v1_board %}, click {% octicon "plus" aria-hidden="true" %} **Add cards**. ![Screenshot showing the header of a project. The "Add cards" button is highlighted with an orange outline.](/assets/images/help/projects/add-cards-button.png) 3. Search for issues and pull requests to add to your {% data variables.projects.projects_v1_board %} using search qualifiers such as `is:issue is:open`. For more information on search qualifiers you can use, see "[AUTOTITLE](/search-github/searching-on-github/searching-issues-and-pull-requests)." @@ -59,7 +59,7 @@ You can put a maximum of 2,500 cards into each project column. If a column has r 1. On the right side of an issue or pull request, click **Projects {% octicon "gear" aria-label="The Gear icon" %}**. ![Screenshot showing an issue's sidebar. The "Projects" section header is highlighted with an orange outline.](/assets/images/help/projects-v2/issue-sidebar-projects.png) - + 2. Click the **Recent**, **Repository**, **User**, or **Organization** tab for the {% data variables.projects.projects_v1_board %} you would like to add to. 3. Type the name of the project in **Filter projects** field. 4. Select one or more {% data variables.projects.projects_v1_boards %} where you want to add the issue or pull request. diff --git a/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md b/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md index c90de26fcc..fc1f2d51e0 100644 --- a/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md +++ b/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md @@ -41,10 +41,10 @@ You can migrate your project boards to the new {% data variables.product.prodnam {% data reusables.projects.enable-migration %} 1. In the top right corner of {% data variables.product.prodname_dotcom_the_website %}, click your profile photo, then click **Your projects**. - + ![Screenshot showing the profile photo menu. The "Your projects" link is highlighted with an orange outline.](/assets/images/help/projects-v2/projects-profile-menu.png) - -1. On the top of your profile page, in the main navigation, click {% octicon "table" aria-label="The project board icon" %} **Projects**. + +1. On the top of your profile page, in the main navigation, click {% octicon "table" aria-hidden="true" %} **Projects**. ![Screenshot showing the tabs on a user profile. The 'Projects' tab is highlighted with an orange outline.](/assets/images/help/projects-v2/tab-projects.png) 1. Above the list of projects, click **Projects (classic)**. {% data reusables.projects.migrate-project-steps %} @@ -59,6 +59,6 @@ You can migrate your project boards to the new {% data variables.product.prodnam {% data reusables.projects.enable-migration %} {% data reusables.repositories.navigate-to-repo %} -1. Under your repository name, click {% octicon "table" aria-label="The project board icon" %} **Projects**. +1. Under your repository name, click {% octicon "table" aria-hidden="true" %} **Projects**. 1. In the left sidebar, click **Projects (classic)**. {% data reusables.projects.migrate-project-steps %} diff --git a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-roadmap-layout.md b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-roadmap-layout.md index 8ab38b51ba..267e34690a 100644 --- a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-roadmap-layout.md +++ b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-roadmap-layout.md @@ -23,7 +23,7 @@ You can set the date or iteration fields that your roadmap will use to position ![Screenshot showing the menu items for a roadmap layout. The "Date fields" button is highlighted with an orange rectangle.](/assets/images/help/projects-v2/roadmap-menu-dates.png) -1. Optionally, to create a new date or iteration field, click {% octicon "plus" aria-label="the plus icon" %} **New field**, type the name of your field, and click **Save**. You can then select the new field or create another. +1. Optionally, to create a new date or iteration field, click {% octicon "plus" aria-hidden="true" %} **New field**, type the name of your field, and click **Save**. You can then select the new field or create another. 1. Select a date or iteration field for "Start date" and "Target date." {% ifversion projects-v2-roadmap-markers %} diff --git a/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md b/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md index 75db40878e..e647f6f5c5 100644 --- a/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md +++ b/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md @@ -81,7 +81,7 @@ Specify a priority for all issues in your project. Next, group all of the items in your project by priority to make it easier to focus on the high priority items. {% data reusables.projects.open-view-menu %} -1. Click {% octicon "rows" aria-label="the rows icon" %} **Group**. +1. Click {% octicon "rows" aria-hidden="true" %} **Group**. 1. Click **Priority**. Now, move issues between groups to change their priority. @@ -121,7 +121,7 @@ When you changed the layout, your project displayed an indicator to show that th To indicate the purpose of the view, give it a descriptive name. {% data reusables.projects.open-view-menu %} -1. Click {% octicon "pencil" aria-label="the pencil icon" %} **Rename view**. +1. Click {% octicon "pencil" aria-hidden="true" %} **Rename view**. 1. Type the new name for your view. 1. To save changes, press Return. @@ -149,7 +149,7 @@ Finally, add a built in workflow to set the status to **Todo** when an item is a 1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing a project's menu bar. The menu icon is highlighted with an orange outline.](/assets/images/help/projects-v2/open-menu.png) -1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**. +1. In the menu, click {% octicon "workflow" aria-hidden="true" %} **Workflows**. 1. Under **Default workflows**, click **Item added to project**. 1. Next to **When**, ensure that both `issues` and `pull requests` are selected. 1. Next to **Set**, select **Status:Todo**. diff --git a/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md b/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md index a887b0ef1c..f629aeebd7 100644 --- a/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md +++ b/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md @@ -15,7 +15,7 @@ You can list relevant projects in a repository. You can only list projects that In order for repository members to see a project listed in a repository, they must have visibility for the project. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)" and "[AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)." 1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your repository. -1. Click {% octicon "table" aria-label="the project icon" %} **Projects**. +1. Click {% octicon "table" aria-hidden="true" %} **Projects**. ![Screenshot showing a repository's tabs. The "Projects" tab is highlighted with an orange outline.](/assets/images/help/projects-v2/repo-tab.png) 1. Click **Add project**. 1. In the search bar that appears, search for projects that are owned by the same user or organization that owns the repository. diff --git a/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/content/issues/tracking-your-work-with-issues/creating-an-issue.md index dac98029be..0733476d0b 100644 --- a/content/issues/tracking-your-work-with-issues/creating-an-issue.md +++ b/content/issues/tracking-your-work-with-issues/creating-an-issue.md @@ -107,7 +107,7 @@ When you create an issue from a discussion, the contents of the discussion post {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. In the right sidebar, click {% octicon "issue-opened" aria-label="The issues icon" %} **Create issue from discussion**. +1. In the right sidebar, click {% octicon "issue-opened" aria-hidden="true" %} **Create issue from discussion**. ![Screenshot of the sidebar in a discussion. The "Create issue from discussion" option is outlined in dark orange.](/assets/images/help/discussions/create-issue-from-discussion.png) diff --git a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md index 3c2a4096ee..12b0e25eac 100644 --- a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md +++ b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md @@ -29,7 +29,7 @@ If you are not using {% data variables.product.prodname_ghe_cloud %}, you can fi {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.compliance %} -1. To the right of the report you want to access, click {% octicon "download" aria-label="The Download icon" %} **Download** or {% octicon "link-external" aria-label="The external link icon" %} **View**. +1. To the right of the report you want to access, click {% octicon "download" aria-hidden="true" %} **Download** or {% octicon "link-external" aria-hidden="true" %} **View**. {% data reusables.security.compliance-report-screenshot %} diff --git a/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md index 7787ba1fc5..193efb238b 100644 --- a/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md +++ b/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md @@ -54,8 +54,9 @@ If a team's access to a {% data variables.projects.projects_v1_board %} is inher {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} -1. Above the team's conversation, click {% octicon "project" aria-label="The Projects icon" %} **Projects**. - ![The team repositories tab](/assets/images/help/organizations/team-project-board-button.png) +1. Above the team's conversation, click {% octicon "project" aria-hidden="true" %} **Projects**. + + ![Screenshot of the main page for a team. In the horizontal navigation bar, the "Projects" tab is outlined in dark orange.](/assets/images/help/organizations/team-project-board-button.png) 1. To change permissions levels, to the right of the {% data variables.projects.projects_v1_board %} you want to update, use the permission level dropdown menu. {% ifversion projects-v2-add-to-team %} diff --git a/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md b/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md index ef40afcec6..ba444cec94 100644 --- a/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md +++ b/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md @@ -13,7 +13,7 @@ permissions: 'Organization owners can allow {% data variables.projects.project_v ## About visibility changes for projects -You can restrict who has the ability to change the visibility of {% data variables.projects.projects_v2_and_v1 %} in your organization, such as restricting members from changing {% data variables.projects.projects_v2_and_v1 %} from private to public. +You can restrict who has the ability to change the visibility of {% data variables.projects.projects_v2_and_v1 %} in your organization, such as restricting members from changing {% data variables.projects.projects_v2_and_v1 %} from private to public. You can limit the ability to change {% data variables.projects.project_v2_and_v1 %} visibility to just organization owners, or you can allow anyone granted admin permissions to change the visibility. @@ -25,7 +25,7 @@ This option may not be available to you if an enterprise owner restricts visibil {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "table" aria-label="The table icon" %} Projects**. +1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "table" aria-hidden="true" %} Projects**. 1. To allow members to adjust project visibility, select **Allow members to change project visibilities for this organization**. 1. Click **Save**. diff --git a/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md index 935a0657c0..4de69b7194 100644 --- a/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md +++ b/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -178,7 +178,7 @@ For each repository in your organization, you can see how much cache storage a r {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the left sidebar, click {% octicon "play" aria-label="The {% data variables.product.prodname_actions %} icon" %} **Actions**, then click **Caches**. +1. In the left sidebar, click {% octicon "play" aria-hidden="true" %} **Actions**, then click **Caches**. 1. Review the list of repositories for information about their {% data variables.product.prodname_actions %} caches. You can click on a repository name to see more detail about the repository's caches. {% ifversion actions-cache-admin-ui %} diff --git a/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md b/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md index 74d189c641..fe12b1f366 100644 --- a/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md +++ b/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md @@ -22,7 +22,7 @@ You can also enable code review limits for individual repositories. If you enabl {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the "Access" section of the sidebar, click **{% octicon "report" aria-label="The report icon" %} Moderation**. +1. In the "Access" section of the sidebar, click **{% octicon "report" aria-hidden="true" %} Moderation**. 1. Under "{% octicon "report" aria-hidden="true" %} Moderation", click **Code review limits**. 1. Review the information on screen. 1. Manage code review limits. diff --git a/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md b/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md index f639ee6979..56deafce20 100644 --- a/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md +++ b/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md @@ -30,7 +30,7 @@ Organization admins can also use the REST API to review and manage {% data varia {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Pending requests**. If any tokens are pending approval for your organization, they will be displayed. +1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Pending requests**. If any tokens are pending approval for your organization, they will be displayed. 1. Click the name of the token that you want to approve or deny. 1. Review the access and permissions that the token is requesting. 1. To grant the token access to the organization, click **Approve**. To deny the token access to the organization, click **Deny**. @@ -40,8 +40,7 @@ Alternatively, you can approve or deny multiple tokens at once: {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Pending requests**. If any tokens are pending approval for your organization, they will be displayed. +1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Pending requests**. If any tokens are pending approval for your organization, they will be displayed. {% data reusables.user-settings.patv2-filters %} 1. Select each token that you want to approve or reject. 1. Select the **request selected...** dropdown menu and click **Approve...** or **Deny...**. - diff --git a/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md b/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md index 38977b1c33..21725e361b 100644 --- a/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md +++ b/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md @@ -18,7 +18,7 @@ Organization owners can only view and revoke {% data variables.product.pat_v2 %} {% ifversion ghec %} Organization owners can also view and revoke {% data variables.product.pat_v1_plural %} if their organization requires SAML single-sign on. For more information, see "[AUTOTITLE](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-authorized-credentials)". For more information about using the REST API to do this, see "[List SAML SSO authorizations for an organization](/rest/orgs/orgs#list-saml-sso-authorizations-for-an-organization)" and "[Remove a SAML SSO authorization for an organization](/rest/orgs/orgs#remove-a-saml-sso-authorization-for-an-organization)."{% endif %} -{% ifversion pat-v2-org-admin-api %} +{% ifversion pat-v2-org-admin-api %} Organization admins can also use the REST API to review and revoke {% data variables.product.pat_v2 %}s. These endpoints can only be called by {% data variables.product.prodname_github_apps %}, and cannot be called with {% data variables.product.pat_generic_plural %} or {% data variables.product.prodname_oauth_apps %}. For more information, see "[AUTOTITLE](/rest/orgs/orgs#list-fine-grained-personal-access-tokens-with-access-to-organization-resources)." @@ -28,7 +28,7 @@ Organization admins can also use the REST API to review and revoke {% data varia {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Active tokens**. Any {% data variables.product.pat_v2 %}s that can access your organization will be displayed. +1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Active tokens**. Any {% data variables.product.pat_v2 %}s that can access your organization will be displayed. 1. Click the name of the token that you want review or revoke. 1. Review the access and permissions that the token has. 1. To revoke access by the token to the organization, click **Revoke**. @@ -37,7 +37,7 @@ Alternatively, you can revoke multiple tokens at once: {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Active tokens**. Any {% data variables.product.pat_v2 %}s that can access your organization will be displayed. +1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Active tokens**. Any {% data variables.product.pat_v2 %}s that can access your organization will be displayed. {% data reusables.user-settings.patv2-filters %} 1. Select each token that you want to revoke. 1. Select the **tokens selected...** dropdown menu and click **Revoke...**. diff --git a/content/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization.md b/content/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization.md index 8b557b1279..cc57dcec84 100644 --- a/content/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization.md +++ b/content/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization.md @@ -16,7 +16,7 @@ Organization owners can prevent {% data variables.product.pat_v2 %}s from access {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Settings**. +1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Settings**. 1. Under **{% data variables.product.pat_v2_caps %}s**, select the option that meets your needs: - **Allow access via {% data variables.product.pat_v2 %}s**: {% data variables.product.pat_v2_caps %}s can access resources owned by the organization. - **Restrict access via {% data variables.product.pat_v2 %}s**: {% data variables.product.pat_v2_caps %}s cannot access resources owned by the organization. SSH keys created by {% data variables.product.pat_v2 %}s will continue to work. @@ -36,7 +36,7 @@ Organization owners can require approval for each {% data variables.product.pat_ {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Settings**. +1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Settings**. 1. Under **Require approval of {% data variables.product.pat_v2 %}s**, select the option that meets your needs: - **Require administrator approval**: An organization owner must approve each {% data variables.product.pat_v2 %} that can access the organization. {% data variables.product.pat_v2_caps %}s created by organization owners will not need approval. - **Do not require administrator approval**: {% data variables.product.pat_v2_caps %}s created by organization members can access resources in the organization without prior approval. @@ -50,7 +50,7 @@ Organization owners can prevent {% data variables.product.pat_v1_plural %} from {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Settings**. +1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Settings**. 1. Under **{% data variables.product.pat_v1_caps %}**, select the option that meets your needs: - **Allow access via {% data variables.product.pat_v1_plural %}**: {% data variables.product.pat_v1_caps_plural %} can access resources owned by the organization. - **Restrict access via {% data variables.product.pat_v1_plural %}**: {% data variables.product.pat_v1_caps_plural %} cannot access resources owned by the organization. SSH keys created by {% data variables.product.pat_v1_plural %} will continue to work. diff --git a/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md index 8fa59be70a..4089788c4a 100644 --- a/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md +++ b/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md @@ -54,7 +54,7 @@ Any team members that have set their status to "Busy" will not be selected for r {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %} {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**. +1. In the left sidebar, click **{% octicon "code-review" aria-hidden="true" %} Code review**. {% else %} 1. In the left sidebar, click **Code review** {% endif %} @@ -69,7 +69,7 @@ Any team members that have set their status to "Busy" will not be selected for r {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %} {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**. +1. In the left sidebar, click **{% octicon "code-review" aria-hidden="true" %} Code review**. {% else %} 1. In the left sidebar, click **Code review** {% endif %} diff --git a/content/packages/learn-github-packages/viewing-packages.md b/content/packages/learn-github-packages/viewing-packages.md index 2bde42af5e..3b07fc1b00 100644 --- a/content/packages/learn-github-packages/viewing-packages.md +++ b/content/packages/learn-github-packages/viewing-packages.md @@ -50,7 +50,7 @@ You can find and view a package located in the repositories of an organization y {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} -3. Under your organization name, click {% octicon "package" aria-label="The package icon" %} **Packages**. +3. Under your organization name, click {% octicon "package" aria-hidden="true" %} **Packages**. {% data reusables.package_registry.navigate-to-packages %} ## Viewing your packages diff --git a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md index 05c7657005..bf08c4b050 100644 --- a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md +++ b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md @@ -25,7 +25,7 @@ It's also possible to verify a domain for your organization{% ifversion ghec %} ## Verifying a domain for your user site {% data reusables.user-settings.access_settings %} -1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-label="The pages icon" %} Pages**. +1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-hidden="true" %} Pages**. {% data reusables.pages.settings-verify-domain-setup %} 1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `USERNAME` with your username and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output. ``` @@ -39,7 +39,7 @@ Organization owners can verify custom domains for their organization. {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-label="The browser icon" %} Pages**. +1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-hidden="true" %} Pages**. {% data reusables.pages.settings-verify-domain-setup %} 1. Wait for your DNS configuration to change. This may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `ORGANIZATION` with the name of your organization and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output. ``` diff --git a/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md index ade1b7f71d..b1590d887e 100644 --- a/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md +++ b/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -38,8 +38,9 @@ To use a shorter and more memorable domain for your privately published site, yo {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %} 3. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** dropdown menu, then select a visibility. -4. To see your published site, under "{% data variables.product.prodname_pages %}", click **{% octicon "link-external" aria-label="The external link icon" %} Visit site**. - ![Screenshot of a confirmation message for {% data variables.product.prodname_pages %} listing the site's URL. To the right of a long blue URL, a button labeled "Visit site" is outlined in dark orange.](/assets/images/help/pages/click-private-pages-url-to-preview.png) +4. To see your published site, under "{% data variables.product.prodname_pages %}", click **{% octicon "link-external" aria-hidden="true" %} Visit site**. + + ![Screenshot of a confirmation message for {% data variables.product.prodname_pages %} listing the site's URL. To the right of a long blue URL, a button labeled "Visit site" is outlined in dark orange.](/assets/images/help/pages/click-private-pages-url-to-preview.png) {% note %} diff --git a/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md index 2cf9a507ba..405f65f802 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md @@ -130,7 +130,7 @@ By default, when you create a new repository in your personal account, workflows You can use the steps below to configure whether {% ifversion internal-actions%}actions and {% endif %}reusable workflows in an internal repository can be accessed from outside the repository.{% ifversion internal-actions %} For more information, see "[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)." Alternatively, you can use the REST API to set, or get details of the level of access. For more information, see "[AUTOTITLE](/rest/actions/permissions#get-the-level-of-access-for-workflows-outside-of-the-repository)" and "[AUTOTITLE](/rest/actions/permissions#set-the-level-of-access-for-workflows-outside-of-the-repository)."{% endif %} 1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the internal repository. -1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. +1. Under your repository name, click {% octicon "gear" aria-hidden="true" %} **Settings**. {% data reusables.repositories.settings-sidebar-actions-general %} 1. Under **Access**, choose one of the access settings: @@ -151,7 +151,7 @@ You can use the steps below to configure whether actions and reusable workflows ### Managing access for a private repository 1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the private repository. -1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. +1. Under your repository name, click {% octicon "gear" aria-hidden="true" %} **Settings**. {% data reusables.repositories.settings-sidebar-actions-general %} 1. Under **Access**, choose one of the access settings: @@ -165,7 +165,7 @@ You can use the steps below to configure whether actions and reusable workflows ### Managing access for a private repository in an organization 1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the private repository. -1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. +1. Under your repository name, click {% octicon "gear" aria-hidden="true" %} **Settings**. {% data reusables.repositories.settings-sidebar-actions-general %} 1. Under **Access**, choose one of the access settings: @@ -178,7 +178,7 @@ You can use the steps below to configure whether actions and reusable workflows {% ifversion fpt %}{% else %} 1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the private repository. -1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. +1. Under your repository name, click {% octicon "gear" aria-hidden="true" %} **Settings**. {% data reusables.repositories.settings-sidebar-actions-general %} 1. Under **Access**, choose one of the access settings: * **Not accessible** - Workflows in other repositories cannot access this repository. diff --git a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md index 244436eb72..a9c1d8a909 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md @@ -23,8 +23,8 @@ Additionally, you can create custom repository roles to allow other groups of us {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. In the "Code and automation" section of the sidebar, click **{% octicon "tag" aria-label="The tag icon" %} Tags**. +1. In the "Code and automation" section of the sidebar, click **{% octicon "tag" aria-hidden="true"%} Tags**. 1. Click **New rule**. -1. Under "Tag name pattern", type the pattern of the tags you want to protect. In this example, typing "\*" protects all tags. +1. Under "Tag name pattern", type the pattern of the tags you want to protect. In this example, typing "\*" protects all tags. ![Screenshot of the "Protected tags / New rule" page. The example pattern `*` is shown with the "Add rule" button. ](/assets/images/help/repository/tag-protection-rule.png) 1. Click **Add rule**. diff --git a/content/repositories/working-with-files/using-files/downloading-source-code-archives.md b/content/repositories/working-with-files/using-files/downloading-source-code-archives.md index 1eddb9733f..f54e538ecd 100644 --- a/content/repositories/working-with-files/using-files/downloading-source-code-archives.md +++ b/content/repositories/working-with-files/using-files/downloading-source-code-archives.md @@ -25,14 +25,14 @@ You can download the source code archives in three ways. ![Screenshot of the list of files on the landing page of a repository. The "Code" button is highlighted with a dark orange outline.](/assets/images/help/repository/code-button.png) -1. Click {% octicon "file-zip" aria-label="The ZIP icon" %} **Download ZIP**. +1. Click {% octicon "file-zip" aria-hidden="true" %} **Download ZIP**. ### Downloading source code archives from a release {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %} 1. Scroll down to the "Assets" section of the release. -1. To download the source code, click {% octicon "file-zip" aria-label="The ZIP icon" %} **Source code (zip)** or {% octicon "file-zip" aria-label="The ZIP icon" %} **Source code (tar.gz)**. +1. To download the source code, click {% octicon "file-zip" aria-hidden="true" %} **Source code (zip)** or {% octicon "file-zip" aria-hidden="true" %} **Source code (tar.gz)**. ### Downloading source code archives from a tag diff --git a/content/search-github/github-code-search/using-github-code-search.md b/content/search-github/github-code-search/using-github-code-search.md index 948311dce9..419a5439ee 100644 --- a/content/search-github/github-code-search/using-github-code-search.md +++ b/content/search-github/github-code-search/using-github-code-search.md @@ -38,7 +38,7 @@ For more information about the search syntax of code search, see "[AUTOTITLE](/s ## Creating and managing saved searches 1. In the top navigation of {% data variables.product.prodname_dotcom_the_website %}, click the search bar and type `saved:`. -1. Under the search bar, the "Saved searches" section should now appear. Click {% octicon "plus-circle" aria-label="The plus-circle icon" %} **Create saved search**. +1. Under the search bar, the "Saved searches" section should now appear. Click {% octicon "plus-circle" aria-hidden="true" %} **Create saved search**. 1. In the pop-up window, fill out the name you want for your query and the query that you want to save. Click **Create saved search**. 1. If you click again on the search bar, you can now see your saved search in the "Saved searches" section under the search bar. Clicking on a saved search entry will add the query to the search bar and filter the suggestions accordingly. - To edit a saved search, in the "Saved searches" section, click {% octicon "pencil" aria-label="The pencil icon" %} to the right of the saved search. diff --git a/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md b/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md index d6ba0742da..b9927bec24 100644 --- a/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md +++ b/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md @@ -16,7 +16,7 @@ shortTitle: Attribute sponsorships --- 1. Navigate to the organization whose sponsorships you want to attribute to another organization. -1. Under your organization name, click {% octicon "heart" aria-label="The heart icon" %} **Sponsoring**. +1. Under your organization name, click {% octicon "heart" aria-hidden="true" %} **Sponsoring**. ![Screenshot of the "{% data variables.product.prodname_dotcom %}" organization's home page. A menu tab, labeled "Sponsoring," is outlined in dark orange.](/assets/images/help/sponsors/sponsoring-tab.png) diff --git a/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md b/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md index ab40fbc875..47b2b94754 100644 --- a/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md +++ b/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md @@ -8,5 +8,5 @@ * **If using an enterprise account**: Navigate to your enterprise account by clicking your profile photo in the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, then clicking **Your enterprises**, then clicking the enterprise. 1. Navigate to the {% data variables.product.prodname_actions %} settings: * **In an organization or repository**: Click **Actions** in the left sidebar, then click **Runners**. - * **If using an enterprise account**: In the left sidebar, click **"{% octicon "law" aria-label="The law icon" %} Policies"**, then click **Actions**, then click the **Runners** tab. + * **If using an enterprise account**: In the left sidebar, click **"{% octicon "law" aria-hidden="true" %} Policies"**, then click **Actions**, then click the **Runners** tab. {% endif %} diff --git a/data/reusables/actions/settings-ui/settings-actions-runner-groups.md b/data/reusables/actions/settings-ui/settings-actions-runner-groups.md index b11801b09a..909a4c95f1 100644 --- a/data/reusables/actions/settings-ui/settings-actions-runner-groups.md +++ b/data/reusables/actions/settings-ui/settings-actions-runner-groups.md @@ -1,5 +1,5 @@ {% comment %}This reusable is only to be used in other repo/org/enterprise setting reusables.{%- endcomment -%} -1. In the left sidebar, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}{% octicon "play" aria-label="The {% data variables.product.prodname_actions %} icon" %} **Actions**, then click **Runner groups**.{% else %}**Actions**.{% ifversion ghes or ghae %} +1. In the left sidebar, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}{% octicon "play" aria-hidden="true" %} **Actions**, then click **Runner groups**.{% else %}**Actions**.{% ifversion ghes or ghae %} 1. In the left sidebar, under "Actions", click **Runner groups**. {%- elsif ghes or ghae %} 1. In the left sidebar, under "Actions", click **Runners**.{% endif %}{% endif %} diff --git a/data/reusables/actions/settings-ui/settings-actions-runners.md b/data/reusables/actions/settings-ui/settings-actions-runners.md index e3cf5ed3cf..15d2ba3e78 100644 --- a/data/reusables/actions/settings-ui/settings-actions-runners.md +++ b/data/reusables/actions/settings-ui/settings-actions-runners.md @@ -1,3 +1,3 @@ {% comment %}This reusable is only to be used in other repo/org/enterprise setting reusables.{%- endcomment -%} -1. In the left sidebar, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}{% octicon "play" aria-label="The {% data variables.product.prodname_actions %} icon" %} **Actions**, then click **Runners**.{% else %}**Actions**.{% ifversion ghes or ghae %} +1. In the left sidebar, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}{% octicon "play" aria-hidden="true" %} **Actions**, then click **Runners**.{% else %}**Actions**.{% ifversion ghes or ghae %} 1. In the left sidebar, under "Actions", click **Runners**.{% endif %}{% endif %} diff --git a/data/reusables/actions/sidebar-secrets-and-variables.md b/data/reusables/actions/sidebar-secrets-and-variables.md index dc0ff2dad4..c783b921d1 100644 --- a/data/reusables/actions/sidebar-secrets-and-variables.md +++ b/data/reusables/actions/sidebar-secrets-and-variables.md @@ -1,5 +1,5 @@ {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 -%} -1. In the "Security" section of the sidebar, select {% ifversion actions-configuration-variables %}**{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets and variables**, {% else %}**{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**, {% endif %}then click **Actions**. +1. In the "Security" section of the sidebar, select {% ifversion actions-configuration-variables %}**{% octicon "key-asterisk" aria-hidden="true" %} Secrets and variables**, {% else %}**{% octicon "key-asterisk" aaria-hidden="true" %} Secrets**, {% endif %}then click **Actions**. {%- else %} 1. In the left sidebar, click **Secrets**. {%- endif %} diff --git a/data/reusables/classroom/assignments-guide-create-the-assignment.md b/data/reusables/classroom/assignments-guide-create-the-assignment.md index 46a1fefcd7..c472861467 100644 --- a/data/reusables/classroom/assignments-guide-create-the-assignment.md +++ b/data/reusables/classroom/assignments-guide-create-the-assignment.md @@ -1,5 +1,5 @@ 1. Sign into {% data variables.product.prodname_classroom_with_url %}. 1. Navigate to a classroom. -1. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, create the assignment. +1. In the {% octicon "repo" aria-hidden="true" %} **Assignments** tab, create the assignment. - If this your first assignment, click **Create an assignment**. - Otherwise, click **New assignment** on the right side. \ No newline at end of file diff --git a/data/reusables/classroom/click-settings.md b/data/reusables/classroom/click-settings.md index 5c670d19c1..8a1c10e2b7 100644 --- a/data/reusables/classroom/click-settings.md +++ b/data/reusables/classroom/click-settings.md @@ -1,3 +1,3 @@ -1. Under the classroom name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. +1. Under the classroom name, click {% octicon "gear" aria-hidden="true" %} **Settings**. ![Screenshot of the tabs in a classroom. The "Settings" tab is outlined in dark orange.](/assets/images/help/classroom/click-settings.png) diff --git a/data/reusables/classroom/click-students.md b/data/reusables/classroom/click-students.md index 62636c33bb..ae017828da 100644 --- a/data/reusables/classroom/click-students.md +++ b/data/reusables/classroom/click-students.md @@ -1,3 +1,3 @@ -1. Under the classroom name, click {% octicon "people" aria-label="The people icon" %} **Students**. +1. Under the classroom name, click {% octicon "people" aria-hidden="true" %} **Students**. ![Screenshot of the tabs in a classroom. The "Students" tab is outlined in dark orange.](/assets/images/help/classroom/click-students.png) diff --git a/data/reusables/codespaces/codespaces-org-policies.md b/data/reusables/codespaces/codespaces-org-policies.md index ccf956a015..c381c23c20 100644 --- a/data/reusables/codespaces/codespaces-org-policies.md +++ b/data/reusables/codespaces/codespaces-org-policies.md @@ -1,3 +1,3 @@ -1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** then click **Policies**. +1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-hidden="true" %} {% data variables.product.prodname_codespaces %}** then click **Policies**. 1. On the "Codespace policies" page, click **Create Policy**. 1. Enter a name for your new policy. diff --git a/data/reusables/codespaces/navigating-to-a-codespace.md b/data/reusables/codespaces/navigating-to-a-codespace.md index 535e548f91..4c98ef4990 100644 --- a/data/reusables/codespaces/navigating-to-a-codespace.md +++ b/data/reusables/codespaces/navigating-to-a-codespace.md @@ -5,4 +5,4 @@ ![Screenshot of a list of two codespaces on GitHub. The codespaces are named "Document codespace navigation" and "Furious snibble."](/assets/images/help/codespaces/click-name-codespace.png) -Alternatively, you can see any of your codespaces for a specific repository by navigating to that repository and selecting **{% octicon "code" aria-label="The code icon" %} Code**. The dropdown menu will display all active codespaces for a repository. +Alternatively, you can see any of your codespaces for a specific repository by navigating to that repository and selecting **{% octicon "code" aria-hidden="true" %} Code**. The dropdown menu will display all active codespaces for a repository. diff --git a/data/reusables/codespaces/sidebar-secret.md b/data/reusables/codespaces/sidebar-secret.md index 324125faba..75b178e2f7 100644 --- a/data/reusables/codespaces/sidebar-secret.md +++ b/data/reusables/codespaces/sidebar-secret.md @@ -1 +1 @@ -1. In the "Security" section of the sidebar, select {% ifversion actions-configuration-variables %}**{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets and variables**, {% else %}**{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**, {% endif %}then click **{% data variables.product.prodname_codespaces %}**. +1. In the "Security" section of the sidebar, select {% ifversion actions-configuration-variables %}**{% octicon "key-asterisk" aria-hidden="true" %} Secrets and variables**, {% else %}**{% octicon "key-asterisk" aria-hidden="true" %} Secrets**, {% endif %}then click **{% data variables.product.prodname_codespaces %}**. diff --git a/data/reusables/copilot/disable-copilot-organization.md b/data/reusables/copilot/disable-copilot-organization.md index 7e1c80dae7..18a82a5078 100644 --- a/data/reusables/copilot/disable-copilot-organization.md +++ b/data/reusables/copilot/disable-copilot-organization.md @@ -1,5 +1,5 @@ {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-label="The copilot icon" %} {% data variables.product.prodname_copilot_short %}**, and then click **Access**. +1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot_short %}**, and then click **Access**. 1. Under "User permissions," to disable {% data variables.product.prodname_copilot %} for all users in your organization, select **Disabled**. 1. To save your changes, click **Save**. \ No newline at end of file diff --git a/data/reusables/copilot/signup-procedure.md b/data/reusables/copilot/signup-procedure.md index 5bb4d04a8a..c06e8fefdc 100644 --- a/data/reusables/copilot/signup-procedure.md +++ b/data/reusables/copilot/signup-procedure.md @@ -1,5 +1,5 @@ {% data reusables.user-settings.access_settings %} -1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-label="The copilot icon" %} {% data variables.product.prodname_copilot %}**. +1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-hidden="true" %} {% data variables.product.prodname_copilot %}**. 1. On the {% data variables.product.prodname_copilot %} settings page, click **Enable {% data variables.product.prodname_copilot %}**. 1. Choose whether you want to pay monthly or yearly, and click **Continue to get access to Copilot**. diff --git a/data/reusables/dependabot/sidebar-secret.md b/data/reusables/dependabot/sidebar-secret.md index 074a7e3b14..11d1b8a550 100644 --- a/data/reusables/dependabot/sidebar-secret.md +++ b/data/reusables/dependabot/sidebar-secret.md @@ -1,5 +1,5 @@ {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the "Security" section of the sidebar, select {% ifversion actions-configuration-variables %}**{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets and variables**, {% else %}**{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**, {% endif %}then click **{% data variables.product.prodname_dependabot %}**. +1. In the "Security" section of the sidebar, select {% ifversion actions-configuration-variables %}**{% octicon "key-asterisk" aria-hidden="true" %} Secrets and variables**, {% else %}**{% octicon "key-asterisk" aria-hidden="true"%} Secrets**, {% endif %}then click **{% data variables.product.prodname_dependabot %}**. {% else %} 1. In the sidebar, click **{% data variables.product.prodname_dependabot %}**. {% endif %} diff --git a/data/reusables/desktop/click-base-branch-in-drop-down.md b/data/reusables/desktop/click-base-branch-in-drop-down.md index a5baa888d6..5b4c322f26 100644 --- a/data/reusables/desktop/click-base-branch-in-drop-down.md +++ b/data/reusables/desktop/click-base-branch-in-drop-down.md @@ -1 +1 @@ -1. At the top of the app, click {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch** and then in the list of branches, click the branch that you want to base your new branch on. +1. At the top of the app, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch** and then in the list of branches, click the branch that you want to base your new branch on. diff --git a/data/reusables/desktop/current-branch-menu.md b/data/reusables/desktop/current-branch-menu.md index f60eb36b70..130d1a4a40 100644 --- a/data/reusables/desktop/current-branch-menu.md +++ b/data/reusables/desktop/current-branch-menu.md @@ -1,3 +1,3 @@ -1. In {% data variables.product.prodname_desktop %}, click {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch**. +1. In {% data variables.product.prodname_desktop %}, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch**. ![Screenshot of the repository bar. A button, labeled "Current Branch" with a downward arrow indicating a dropdown menu, is outlined in orange.](/assets/images/help/desktop/current-branch-menu.png) diff --git a/data/reusables/desktop/navigate-to-stashed-changes.md b/data/reusables/desktop/navigate-to-stashed-changes.md index 6ecf48249b..db4d2262a6 100644 --- a/data/reusables/desktop/navigate-to-stashed-changes.md +++ b/data/reusables/desktop/navigate-to-stashed-changes.md @@ -1,3 +1,3 @@ -1. If you are not already on the branch where the changes are stashed, in the repository bar, click {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch**, then click the branch with stashed changes. +1. If you are not already on the branch where the changes are stashed, in the repository bar, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch**, then click the branch with stashed changes. ![Screenshot of the "Current Branch" dropdown view. Under "Recent Branches", a branch, named "my-feature", is highlighted with an orange outline.](/assets/images/help/desktop/select-branch-from-dropdown.png) diff --git a/data/reusables/desktop/select-branch-to-delete.md b/data/reusables/desktop/select-branch-to-delete.md index 730cb26f00..074b755579 100644 --- a/data/reusables/desktop/select-branch-to-delete.md +++ b/data/reusables/desktop/select-branch-to-delete.md @@ -1 +1 @@ -1. In the repository bar, click {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch**, then click the branch that you want to delete. +1. In the repository bar, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch**, then click the branch that you want to delete. diff --git a/data/reusables/discussions/discussions-tab.md b/data/reusables/discussions/discussions-tab.md index 1649ebf2d7..e5c957bfbd 100644 --- a/data/reusables/discussions/discussions-tab.md +++ b/data/reusables/discussions/discussions-tab.md @@ -1,3 +1,3 @@ -1. Under your repository or organization name, click {% octicon "comment-discussion" aria-label="The discussion icon" %} **Discussions**. +1. Under your repository or organization name, click {% octicon "comment-discussion" aria-hidden="true" %} **Discussions**. ![Screenshot of the tabs in a {% data variables.product.company_short %} repository. The "Discussions" option is outlined in dark orange.](/assets/images/help/discussions/repository-discussions-tab.png) diff --git a/data/reusables/discussions/starting-a-poll.md b/data/reusables/discussions/starting-a-poll.md index ec2ed52621..62720b1466 100644 --- a/data/reusables/discussions/starting-a-poll.md +++ b/data/reusables/discussions/starting-a-poll.md @@ -11,7 +11,7 @@ 1. Under "Poll question", type a question for your poll. 1. Under "Poll options", type at least two options for your poll. -1. Optionally, to add an extra poll option, click **{% octicon "plus" aria-label="The plus icon" %} Add an option**. +1. Optionally, to add an extra poll option, click **{% octicon "plus" aria-hidden="true" %} Add an option**. ![Screenshot of the page to start a new poll. The plus icon and "Add an option" are outlined in dark orange.](/assets/images/help/discussions/new-poll-add-option.png) diff --git a/data/reusables/enterprise-accounts/actions-tab.md b/data/reusables/enterprise-accounts/actions-tab.md index 5a2db16745..0985def0f8 100644 --- a/data/reusables/enterprise-accounts/actions-tab.md +++ b/data/reusables/enterprise-accounts/actions-tab.md @@ -1 +1 @@ -1. Under "{% octicon "law" aria-label="The law icon" %} Policies", click **Actions**. +1. Under "{% octicon "law" aria-hidden="true" %} Policies", click **Actions**. diff --git a/data/reusables/enterprise-accounts/copilot-tab.md b/data/reusables/enterprise-accounts/copilot-tab.md index 4d5bdec7b2..79c469b085 100644 --- a/data/reusables/enterprise-accounts/copilot-tab.md +++ b/data/reusables/enterprise-accounts/copilot-tab.md @@ -1 +1 @@ -1. Under "{% octicon "law" aria-label="The law icon" %} Policies", click **{% data variables.product.prodname_copilot_short %}**. +1. Under "{% octicon "law" aaria-hidden="true" %} Policies", click **{% data variables.product.prodname_copilot_short %}**. diff --git a/data/reusables/enterprise-accounts/options-tab.md b/data/reusables/enterprise-accounts/options-tab.md index c2f65d4286..db4daa0312 100644 --- a/data/reusables/enterprise-accounts/options-tab.md +++ b/data/reusables/enterprise-accounts/options-tab.md @@ -1 +1 @@ -1. Under {% ifversion ghes or ghae %} {% octicon "law" aria-label="The law icon" %} **Policies**{% else %}"{% octicon "gear" aria-label="The Settings gear" %} Settings"{% endif %}, click **Options**. +1. Under {% ifversion ghes or ghae %} {% octicon "law" aria-hidden="true" %} **Policies**{% else %}"{% octicon "gear" aria-hidden="true" %} Settings"{% endif %}, click **Options**. diff --git a/data/reusables/enterprise-accounts/pages-tab.md b/data/reusables/enterprise-accounts/pages-tab.md index 423b42934f..1511308e9e 100644 --- a/data/reusables/enterprise-accounts/pages-tab.md +++ b/data/reusables/enterprise-accounts/pages-tab.md @@ -1 +1 @@ -1. Under "{% octicon "law" aria-label="The law icon" %} Policies", click **Pages**. +1. Under "{% octicon "law" aria-hidden="true" %} Policies", click **Pages**. diff --git a/data/reusables/organizations/billing-settings.md b/data/reusables/organizations/billing-settings.md index 6456fb0651..f93bf34bba 100644 --- a/data/reusables/organizations/billing-settings.md +++ b/data/reusables/organizations/billing-settings.md @@ -1,4 +1,4 @@ {% data reusables.user-settings.access_settings %} -1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**. +1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-hidden="true" %} Organizations**. {% data reusables.profile.org_settings %} -1. If you are an organization owner, in the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit-card icon" %} Billing and plans**. +1. If you are an organization owner, in the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**. diff --git a/data/reusables/organizations/billing_plans.md b/data/reusables/organizations/billing_plans.md index bba7f92960..0be2379c8a 100644 --- a/data/reusables/organizations/billing_plans.md +++ b/data/reusables/organizations/billing_plans.md @@ -1 +1 @@ -1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**. \ No newline at end of file +1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**. \ No newline at end of file diff --git a/data/reusables/organizations/block_users.md b/data/reusables/organizations/block_users.md index 60ace89469..ba3f48fa04 100644 --- a/data/reusables/organizations/block_users.md +++ b/data/reusables/organizations/block_users.md @@ -1 +1 @@ -1. In the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**, then click **Blocked users**. +1. In the sidebar, select **{% octicon "report" aria-hidden="true"%} Moderation**, then click **Blocked users**. diff --git a/data/reusables/organizations/click-codespaces.md b/data/reusables/organizations/click-codespaces.md index 2f409b474f..6254d36b5c 100644 --- a/data/reusables/organizations/click-codespaces.md +++ b/data/reusables/organizations/click-codespaces.md @@ -1 +1 @@ -1. In the left sidebar, click **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**. +1. In the left sidebar, click **{% octicon "codespaces" aria-hidden="true" %} Codespaces**. diff --git a/data/reusables/organizations/compliance.md b/data/reusables/organizations/compliance.md index 2d51898344..dff64e523e 100644 --- a/data/reusables/organizations/compliance.md +++ b/data/reusables/organizations/compliance.md @@ -1 +1 @@ -1. In the "Security" section of the sidebar, click **{% octicon "checklist" aria-label="The checklist icon" %} Compliance**. +1. In the "Security" section of the sidebar, click **{% octicon "checklist" aria-hidden="true" %} Compliance**. diff --git a/data/reusables/organizations/github-apps-settings-sidebar.md b/data/reusables/organizations/github-apps-settings-sidebar.md index 3ec3846696..cc3a313249 100644 --- a/data/reusables/organizations/github-apps-settings-sidebar.md +++ b/data/reusables/organizations/github-apps-settings-sidebar.md @@ -1,5 +1,5 @@ {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the left sidebar, select **{% octicon "code" aria-label="The code icon" %} Developer settings** then click **{% data variables.product.prodname_github_apps %}**. +1. In the left sidebar, select **{% octicon "code" aria-hidden="true" %} Developer settings** then click **{% data variables.product.prodname_github_apps %}**. {% else %} 1. In the left sidebar, click **{% data variables.product.prodname_github_apps %}**. {% endif %} diff --git a/data/reusables/organizations/mixed-roles-warning.md b/data/reusables/organizations/mixed-roles-warning.md index 31f89c2eab..f2af1e91a1 100644 --- a/data/reusables/organizations/mixed-roles-warning.md +++ b/data/reusables/organizations/mixed-roles-warning.md @@ -1 +1 @@ -If a person has been given conflicting access, you'll see a warning on the repository access page. The warning appears with "{% octicon "alert" aria-label="The alert icon" %} Mixed roles" next to the person with the conflicting access. To see the source of the conflicting access, hover over the warning icon or click **Mixed roles**. +If a person has been given conflicting access, you'll see a warning on the repository access page. The warning appears with "{% octicon "alert" aria-hidden="true" %} Mixed roles" next to the person with the conflicting access. To see the source of the conflicting access, hover over the warning icon or click **Mixed roles**. diff --git a/data/reusables/organizations/org-settings-repository-roles.md b/data/reusables/organizations/org-settings-repository-roles.md index 937618670b..f34b3574e1 100644 --- a/data/reusables/organizations/org-settings-repository-roles.md +++ b/data/reusables/organizations/org-settings-repository-roles.md @@ -1 +1 @@ -1. In the "Access" section of the sidebar, click **{% octicon "id-badge" aria-label="The ID badge icon" %} Repository roles**. +1. In the "Access" section of the sidebar, click **{% octicon "id-badge" aria-hidden="true" %} Repository roles**. diff --git a/data/reusables/organizations/teams_sidebar.md b/data/reusables/organizations/teams_sidebar.md index cf642496dc..9adb75ae34 100644 --- a/data/reusables/organizations/teams_sidebar.md +++ b/data/reusables/organizations/teams_sidebar.md @@ -1,5 +1,5 @@ {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the "Access" section of the sidebar, click **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Team discussions**. +1. In the "Access" section of the sidebar, click **{% octicon "comment-discussion" aria-hidden="true" %} Team discussions**. {% else %} 1. In the Settings sidebar, click **Teams**. {% endif %} diff --git a/data/reusables/pages/sidebar-pages.md b/data/reusables/pages/sidebar-pages.md index aaa23707d9..b451160d5a 100644 --- a/data/reusables/pages/sidebar-pages.md +++ b/data/reusables/pages/sidebar-pages.md @@ -1,5 +1,5 @@ {% ifversion fpt or ghes > 3.4 or ghec or ghae > 3.4 %} -1. In the "Code and automation" section of the sidebar, click **{% octicon "browser" aria-label="The browser icon" %} Pages**. +1. In the "Code and automation" section of the sidebar, click **{% octicon "browser" aria-hidden="true" %} Pages**. {% else %} 1. In the left sidebar, click **Pages**. {% endif %} diff --git a/data/reusables/pages/visit-site.md b/data/reusables/pages/visit-site.md index bd60fcca76..c9853e659e 100644 --- a/data/reusables/pages/visit-site.md +++ b/data/reusables/pages/visit-site.md @@ -1,4 +1,4 @@ -1. To see your published site, under "{% data variables.product.prodname_pages %}", click **{% octicon "link-external" aria-label="The external link icon" %} Visit site**. +1. To see your published site, under "{% data variables.product.prodname_pages %}", click **{% octicon "link-external" aria-hidden="true" %} Visit site**. ![Screenshot of a confirmation message for {% data variables.product.prodname_pages %} listing the site's URL. To the right of the URL, a button labeled "Visit site" is outlined in dark orange.](/assets/images/help/pages/click-pages-url-to-preview.png) {% note %} diff --git a/data/reusables/project-management/click-menu.md b/data/reusables/project-management/click-menu.md index e95bfdceb8..2a491bd58d 100644 --- a/data/reusables/project-management/click-menu.md +++ b/data/reusables/project-management/click-menu.md @@ -1 +1 @@ -1. On the top-right side of the {% data variables.projects.projects_v1_board %}, click {% octicon "three-bars" aria-label="The three-bars octicon" %} **Menu**. +1. On the top-right side of the {% data variables.projects.projects_v1_board %}, click {% octicon "three-bars" aria-hidden="true" %} **Menu**. diff --git a/data/reusables/project-management/link-repos-to-project-board.md b/data/reusables/project-management/link-repos-to-project-board.md index 6bce91fd71..a677ca4e6e 100644 --- a/data/reusables/project-management/link-repos-to-project-board.md +++ b/data/reusables/project-management/link-repos-to-project-board.md @@ -1 +1 @@ -You can link up to twenty-five repositories to your organization or user-owned {% data variables.projects.projects_v1_board %}. Linking repositories makes it easier to add issues and pull requests from those repositories to your {% data variables.projects.projects_v1_board %} using **{% octicon "plus" aria-label="The Plus icon" %} Add cards** or from the issue or pull requests sidebar. +You can link up to twenty-five repositories to your organization or user-owned {% data variables.projects.projects_v1_board %}. Linking repositories makes it easier to add issues and pull requests from those repositories to your {% data variables.projects.projects_v1_board %} using **{% octicon "plus" aria-hidden="true" %} Add cards** or from the issue or pull requests sidebar. diff --git a/data/reusables/projects/access-workflows.md b/data/reusables/projects/access-workflows.md index 060b05ce7b..86264d3924 100644 --- a/data/reusables/projects/access-workflows.md +++ b/data/reusables/projects/access-workflows.md @@ -2,5 +2,5 @@ 1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing a project's menu bar. The menu icon is highlighted with an orange outline.](/assets/images/help/projects-v2/open-menu.png) - -1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**. + +1. In the menu, click {% octicon "workflow" aria-hidden="true" %} **Workflows**. diff --git a/data/reusables/projects/customize/sort.md b/data/reusables/projects/customize/sort.md index fc1cf59858..af8a9f6df8 100644 --- a/data/reusables/projects/customize/sort.md +++ b/data/reusables/projects/customize/sort.md @@ -1,10 +1,10 @@ {% data reusables.projects.open-view-menu %} 1. Click **Sort**. 1. Click the field you want to sort by. -1. Optionally, to change the direction of the sort, click {% octicon "sort-desc" aria-hidden="true" %}. +1. Optionally, to change the direction of the sort, click the field again. ![Screenshot of the sort menu. The button to change the direction of the sort is highlighted with an orange outline.](/assets/images/help/projects-v2/sort-order.png) - -1. Optionally, to remove a sort, click {% octicon "x" aria-label="the x icon" %} **No sorting** at the bottom of the list. + +1. Optionally, to remove a sort, click {% octicon "x" aria-hidden="true" %} **No sorting** at the bottom of the list. Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Sort by." diff --git a/data/reusables/projects/customize/sum.md b/data/reusables/projects/customize/sum.md index 55a9807f7d..201bdafcd0 100644 --- a/data/reusables/projects/customize/sum.md +++ b/data/reusables/projects/customize/sum.md @@ -3,5 +3,5 @@ You can configure a view to show the sum of one of more number fields, including In a board layout, field sums are displayed at the top of each column. In table{% ifversion projects-v2-roadmaps %} and roadmap layouts{% else %} layout{% endif %}, when you enable grouping by a field, field sums are included in each group's header. {% data reusables.projects.open-view-menu %} -1. Click {% octicon "number" aria-label="the number icon" %} **Field sum**. +1. Click {% octicon "number" aria-hidden="true" %} **Field sum**. 1. Select the fields you want to include. diff --git a/data/reusables/reminders/scheduled-reminders.md b/data/reusables/reminders/scheduled-reminders.md index b45b072c3c..cf950f1aa0 100644 --- a/data/reusables/reminders/scheduled-reminders.md +++ b/data/reusables/reminders/scheduled-reminders.md @@ -1 +1 @@ -1. In the "Integrations" section of the sidebar, click **{% octicon "clock" aria-label="The clock icon" %} Scheduled reminders**. +1. In the "Integrations" section of the sidebar, click **{% octicon "clock" aria-hidden="true" %} Scheduled reminders**. diff --git a/data/reusables/repositories/actions-cache-list.md b/data/reusables/repositories/actions-cache-list.md index b4f057bc84..7e9e472333 100644 --- a/data/reusables/repositories/actions-cache-list.md +++ b/data/reusables/repositories/actions-cache-list.md @@ -1 +1 @@ -1. In the left sidebar, under the "Management" section, click {% octicon "cache" aria-label="The Cache icon" %} **Caches**. +1. In the left sidebar, under the "Management" section, click {% octicon "cache" aria-hidden="true" %} **Caches**. diff --git a/data/reusables/repositories/actions-tab.md b/data/reusables/repositories/actions-tab.md index 046a6a2d42..702fc2cff6 100644 --- a/data/reusables/repositories/actions-tab.md +++ b/data/reusables/repositories/actions-tab.md @@ -1,2 +1,2 @@ -1. Under your repository name, click {% octicon "play" aria-label="The Play icon" %} **Actions**. +1. Under your repository name, click {% octicon "play" aria-hidden="true" %} **Actions**. ![Actions tab in the main repository navigation](/assets/images/help/repository/actions-tab.png) diff --git a/data/reusables/repositories/changed-files.md b/data/reusables/repositories/changed-files.md index 7533c129fe..8b98e76c7e 100644 --- a/data/reusables/repositories/changed-files.md +++ b/data/reusables/repositories/changed-files.md @@ -1,3 +1,3 @@ -1. On the pull request, click {% octicon "file-diff" aria-label="The file diff icon" %} **Files changed**. +1. On the pull request, click {% octicon "file-diff" aria-hidden="true" %} **Files changed**. ![Screenshot of the tabs for a pull request. The "Changed" tab is outlined in dark orange.](/assets/images/help/pull_requests/pull-request-tabs-changed-files.png) diff --git a/data/reusables/repositories/review-pr-commits.md b/data/reusables/repositories/review-pr-commits.md index 9fd62e7bc4..9b96a78785 100644 --- a/data/reusables/repositories/review-pr-commits.md +++ b/data/reusables/repositories/review-pr-commits.md @@ -1,3 +1,3 @@ -1. On the pull request, click {% octicon "git-commit" aria-label="The commit icon" %} **Commits**. +1. On the pull request, click {% octicon "git-commit" aria-hidden="true" %} **Commits**. ![Screenshot of the title and tabs on a pull request. The "Commits" tab is outlined in dark orange.](/assets/images/help/pull_requests/pull-request-tabs-commits.png) diff --git a/data/reusables/repositories/sidebar-moderation-reported-content.md b/data/reusables/repositories/sidebar-moderation-reported-content.md index 6d184ae816..3873a7ad31 100644 --- a/data/reusables/repositories/sidebar-moderation-reported-content.md +++ b/data/reusables/repositories/sidebar-moderation-reported-content.md @@ -1 +1 @@ -1. In the "Access" section of the sidebar, select **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Moderation options**, then click **Reported content**. +1. In the "Access" section of the sidebar, select **{% octicon "comment-discussion" aria-hidden="true" %} Moderation options**, then click **Reported content**. diff --git a/data/reusables/repositories/sidebar-notifications.md b/data/reusables/repositories/sidebar-notifications.md index 01d0705702..7e81ae9b6a 100644 --- a/data/reusables/repositories/sidebar-notifications.md +++ b/data/reusables/repositories/sidebar-notifications.md @@ -1,5 +1,5 @@ {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the "Integrations" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Email notifications**. +1. In the "Integrations" section of the sidebar, click **{% octicon "mail" aria-hidden="true" %} Email notifications**. {% else %} 1. Click **Notifications**. {% endif %} diff --git a/data/reusables/user-settings/access_applications.md b/data/reusables/user-settings/access_applications.md index 8d2e3d4c14..986e15c7aa 100644 --- a/data/reusables/user-settings/access_applications.md +++ b/data/reusables/user-settings/access_applications.md @@ -1,5 +1,5 @@ {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} Applications**. +1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-hidden="true" %} Applications**. {% else %} 1. In the left sidebar, click **Applications**. {% endif %} diff --git a/data/reusables/user-settings/accessibility_settings.md b/data/reusables/user-settings/accessibility_settings.md index 2c9e37e2f4..602884da4e 100644 --- a/data/reusables/user-settings/accessibility_settings.md +++ b/data/reusables/user-settings/accessibility_settings.md @@ -1 +1 @@ -1. In the left sidebar, click **{% octicon "accessibility" aria-label="The accessibility icon" %} Accessibility**. +1. In the left sidebar, click **{% octicon "accessibility" aria-hidden="true" %} Accessibility**. diff --git a/data/reusables/user-settings/account_settings.md b/data/reusables/user-settings/account_settings.md index 68eff5cd0f..3e7aa168e6 100644 --- a/data/reusables/user-settings/account_settings.md +++ b/data/reusables/user-settings/account_settings.md @@ -1,5 +1,5 @@ {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the left sidebar, click **{% octicon "gear" aria-label="The gear icon" %} Account**. +1. In the left sidebar, click **{% octicon "gear" aria-hidden="true" %} Account**. {% else %} 1. In the left sidebar, click **Account**. {% endif %} diff --git a/data/reusables/user-settings/appearance-settings.md b/data/reusables/user-settings/appearance-settings.md index 51e49bc7cc..216989ffd5 100644 --- a/data/reusables/user-settings/appearance-settings.md +++ b/data/reusables/user-settings/appearance-settings.md @@ -1,5 +1,5 @@ {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**. +1. In the left sidebar, click **{% octicon "paintbrush" aria-hidden="true" %} Appearance**. {% else %} 1. In the user settings sidebar, click **Appearance**. {% endif %} diff --git a/data/reusables/user-settings/billing_plans.md b/data/reusables/user-settings/billing_plans.md index 8e2fe9c7d4..75ab1a3abe 100644 --- a/data/reusables/user-settings/billing_plans.md +++ b/data/reusables/user-settings/billing_plans.md @@ -1 +1 @@ -1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit-card icon" %} Billing and plans**, then click **Plans and usage**. +1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**, then click **Plans and usage**. diff --git a/data/reusables/user-settings/billing_plans_payment.md b/data/reusables/user-settings/billing_plans_payment.md index 8c7f471a0d..2ed8b68088 100644 --- a/data/reusables/user-settings/billing_plans_payment.md +++ b/data/reusables/user-settings/billing_plans_payment.md @@ -1 +1 @@ -1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit-card icon" %} Billing and plans**, then click **Payment information**. +1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**, then click **Payment information**. diff --git a/data/reusables/user-settings/billing_plans_spending.md b/data/reusables/user-settings/billing_plans_spending.md index 3aea44c19a..0495c24aca 100644 --- a/data/reusables/user-settings/billing_plans_spending.md +++ b/data/reusables/user-settings/billing_plans_spending.md @@ -1 +1 @@ -1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit-card icon" %} Billing and plans**, then click **Spending limits**. +1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**, then click **Spending limits**. diff --git a/data/reusables/user-settings/blocked_users.md b/data/reusables/user-settings/blocked_users.md index b7ba502dca..7d9b674c27 100644 --- a/data/reusables/user-settings/blocked_users.md +++ b/data/reusables/user-settings/blocked_users.md @@ -1 +1 @@ -1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation** then click **Blocked users**. +1. In the "Access" section of the sidebar, select **{% octicon "report" aria-hidden="true" %} Moderation** then click **Blocked users**. diff --git a/data/reusables/user-settings/codespaces-tab.md b/data/reusables/user-settings/codespaces-tab.md index 5aa532885e..dd0058d669 100644 --- a/data/reusables/user-settings/codespaces-tab.md +++ b/data/reusables/user-settings/codespaces-tab.md @@ -1 +1 @@ -1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**. +1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "codespaces" aria-hidden="true" %} Codespaces**. diff --git a/data/reusables/user-settings/copilot-settings.md b/data/reusables/user-settings/copilot-settings.md index 06e7458a7c..1d81afb309 100644 --- a/data/reusables/user-settings/copilot-settings.md +++ b/data/reusables/user-settings/copilot-settings.md @@ -1 +1 @@ -1. In the left sidebar, click **{% octicon "copilot" aria-label="The copilot icon" %} GitHub Copilot**. +1. In the left sidebar, click **{% octicon "copilot" aria-hidden="true" %} GitHub Copilot**. diff --git a/data/reusables/user-settings/emails.md b/data/reusables/user-settings/emails.md index c7a6639644..bd75f73f7a 100644 --- a/data/reusables/user-settings/emails.md +++ b/data/reusables/user-settings/emails.md @@ -1,5 +1,5 @@ {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the "Access" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Emails**. +1. In the "Access" section of the sidebar, click **{% octicon "mail" aria-hidden="true" %} Emails**. {% else %} 1. In the left sidebar, click **Emails**. {% endif %} diff --git a/data/reusables/user-settings/organizations.md b/data/reusables/user-settings/organizations.md index 20e148d3a2..b96e600902 100644 --- a/data/reusables/user-settings/organizations.md +++ b/data/reusables/user-settings/organizations.md @@ -1,5 +1,5 @@ {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**. +1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-hidden="true" %} Organizations**. {% else %} 1. In your user settings sidebar, click **Organizations**. {% endif %} diff --git a/data/reusables/user-settings/repo-tab.md b/data/reusables/user-settings/repo-tab.md index bed043bfcb..307d9d3811 100644 --- a/data/reusables/user-settings/repo-tab.md +++ b/data/reusables/user-settings/repo-tab.md @@ -1,5 +1,5 @@ {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**. +1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "repo" aaria-hidden="true" %} Repositories**. {% else %} 1. In the left sidebar, click **Repositories**. {% endif %} diff --git a/data/reusables/user-settings/saved_replies.md b/data/reusables/user-settings/saved_replies.md index e7cb489ad9..0673ab3417 100644 --- a/data/reusables/user-settings/saved_replies.md +++ b/data/reusables/user-settings/saved_replies.md @@ -1,5 +1,5 @@ {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "reply" aria-label="The reply icon" %} Saved replies**. +1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "reply" aria-hidden="true" %} Saved replies**. {% else %} 1. In the left sidebar, click **Saved replies**. {% endif %} diff --git a/data/reusables/user-settings/security-analysis.md b/data/reusables/user-settings/security-analysis.md index cec03ed772..4728a5741c 100644 --- a/data/reusables/user-settings/security-analysis.md +++ b/data/reusables/user-settings/security-analysis.md @@ -1,5 +1,5 @@ {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Code security and analysis**. +1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-hidden="true"%} Code security and analysis**. {% else %} 1. In the left sidebar, click **Security & analysis**. {% endif %} diff --git a/data/reusables/user-settings/security.md b/data/reusables/user-settings/security.md index 444ca965fa..c58a1535da 100644 --- a/data/reusables/user-settings/security.md +++ b/data/reusables/user-settings/security.md @@ -1,5 +1,5 @@ {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the "Access" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Password and authentication**. +1. In the "Access" section of the sidebar, click **{% octicon "shield-lock" aria-hidden="true" %} Password and authentication**. {% else %} 1. In the left sidebar, click **Account security**. {% endif %} diff --git a/data/reusables/user-settings/sessions.md b/data/reusables/user-settings/sessions.md index 472a4af491..45da7e6314 100644 --- a/data/reusables/user-settings/sessions.md +++ b/data/reusables/user-settings/sessions.md @@ -1 +1 @@ -1. In the "Access" section of the sidebar, click **{% octicon "broadcast" aria-label="The broadcast icon" %} Sessions**. +1. In the "Access" section of the sidebar, click **{% octicon "broadcast" aria-hidden="true" %} Sessions**. diff --git a/data/reusables/user-settings/ssh.md b/data/reusables/user-settings/ssh.md index ec12893cd0..37f5c59b9f 100644 --- a/data/reusables/user-settings/ssh.md +++ b/data/reusables/user-settings/ssh.md @@ -1,5 +1,5 @@ {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the "Access" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} SSH and GPG keys**. +1. In the "Access" section of the sidebar, click **{% octicon "key" aria-hidden="true" %} SSH and GPG keys**. {% else %} 1. In the user settings sidebar, click **SSH and GPG keys**. {% endif %}