Merge pull request #57101 from github/repo-sync

Repo sync

Author: docs-bot

content/actions/concepts/security/openid-connect.md

@@ -20,7 +20,7 @@ redirect_from:
 
 However, using hardcoded secrets requires you to create credentials in the cloud provider and then duplicate them in {% data variables.product.prodname_dotcom %} as a secret.
 
-After you have established a trust connection with a cloud provider that supports OIDC, you can you can configure your workflow to request a short-lived access token directly from the cloud provider.
+After you have established a trust connection with a cloud provider that supports OIDC, you can configure your workflow to request a short-lived access token directly from the cloud provider.
 
 ## Benefits of using OIDC
 

content/education/about-github-education/use-github-at-your-educational-institution/applying-to-be-a-github-campus-expert.md

@@ -10,7 +10,7 @@ redirect_from:
 
 ## Applying to the {% data variables.product.prodname_student_leader_program %} program
 
-To apply to the {% data variables.product.prodname_student_leader_program %} program, you must first submit an application form, then submit a video resume. Applications to the program open in February and August, and you’ll have a full month to apply.
+To apply to the {% data variables.product.prodname_student_leader_program %} program, you must first submit an application form, then submit a video resume. Applications to the program open every July, and you’ll have a full month to apply.
 
 > [!NOTE]
 > The application process helps us get to know the applicant. Here are some things we want to learn about you:

content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md

@@ -1,5 +1,6 @@
 ---
-title: About READMEs
+title: About the repository README file
+shortTitle: About READMEs
 intro: 'You can add a README file to your repository to tell other people why your project is useful, what they can do with your project, and how they can use it.'
 redirect_from:
   - /articles/section-links-on-readmes-and-blob-pages
@@ -35,25 +36,25 @@ When your README is viewed on GitHub, any content beyond 500 KiB will be truncat
 
 {% data reusables.profile.profile-readme %}
 
-## Auto-generated table of contents for README files
+## Auto-generated table of contents for markdown files
 
 For the rendered view of any Markdown file in a repository, including README files, {% data variables.product.github %} will automatically generate a table of contents based on section headings. You can view the table of contents for a README file by clicking the {% octicon "list-unordered" aria-label="Table of Contents" %} menu icon at the top left of the rendered page.
 
 ![Screenshot of the README for a repository. In the upper-left corner, the "Table of contents" dropdown menu (list icon) is expanded.](/assets/images/help/repository/readme-automatic-toc.png)
 
-## Section links in README files and blob pages
+## Section links in markdown files and blob pages
 
 {% data reusables.repositories.section-links %}
 
 For more detailed information about section links, see [Section links](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#section-links).
 
-## Relative links and image paths in README files
+## Relative links and image paths in markdown files
 
 {% data reusables.repositories.relative-links %}
 
 ## Wikis
 
-A README should contain only the necessary information for developers to get started using and contributing to your project. Longer documentation is best suited for wikis. For more information, see [AUTOTITLE](/communities/documenting-your-project-with-wikis/about-wikis).
+A README should only contain information necessary for developers to get started using and contributing to your project. Longer documentation is best suited for wikis. For more information, see [AUTOTITLE](/communities/documenting-your-project-with-wikis/about-wikis).
 
 ## Further reading
 

content/support/contacting-github-support/creating-a-support-ticket.md

@@ -23,7 +23,7 @@ topics:
   - Support
 ---
 
-## About support tickets
+## About support tickets 
 
 {% ifversion fpt %}
 {% data reusables.support.free-and-paid-support %}
@@ -83,6 +83,10 @@ Especially for tickets with {% data variables.product.support_ticket_priority_ur
 1. Navigate to the {% data variables.contact.contact_landing_page_portal %} and choose one of the following options:
 
    * To sign in with your {% data variables.product.github %} account, click **Sign in with {% data variables.product.github %}**.
+   * If your organization uses {% data variables.enterprise.data_residency_short %} or {% data variables.enterprise.prodname_managed_users %} (accounts ending in `.ghe`):
+      1. In the sign-in dialog, click **Sign in to your .ghe account**.
+      1. Enter your enterprise or tenant name (provided by your administrator) and continue.
+      1. Complete the SAML authentication process as prompted. This will sign you in to your .ghe enterprise-managed account.
    * To sign up for {% data variables.product.github %}, click **Sign up for {% data variables.product.github %}**.
    * If you can't sign in or sign up, click **Can't sign in?** and fill out the form. You will be guided through an email verification process.{% ifversion ghec or ghes %} You will need to upload your {% data variables.product.prodname_enterprise %} license. For more information, see [AUTOTITLE](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise).{% endif %}