Skip to content

Comments

Adding .ghe support ticket creation steps#39744

Merged
Sharra-writes merged 7 commits intogithub:mainfrom
adamrr724:patch-10
Aug 12, 2025
Merged

Adding .ghe support ticket creation steps#39744
Sharra-writes merged 7 commits intogithub:mainfrom
adamrr724:patch-10

Conversation

@adamrr724
Copy link
Contributor

@adamrr724 adamrr724 commented Aug 8, 2025 •
edited
Loading

Why:

Closes: https://github.com/github/docs-content/issues/19210

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing and the changes look good in the review environment.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Aug 8, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Aug 8, 2025 •
edited
Loading

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
support/contacting-github-support/creating-a-support-ticket.md fpt
ghec
ghes@ 3.17 3.16 3.15 3.14
fpt
ghec
ghes@ 3.17 3.16 3.15 3.14

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

@adamrr724
Update support ticket creation instructions
923af97 
Added instructions for signing in with .ghe accounts.
@adamrr724 adamrr724 marked this pull request as ready for review August 8, 2025 22:10
Copilot AI review requested due to automatic review settings August 8, 2025 22:10
Copilot AI reviewed Aug 8, 2025
View reviewed changes
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds specific instructions for users with Data Residency or Enterprise Managed Users (EMU) accounts to the support ticket creation documentation. The change provides a clear step-by-step process for signing in with .ghe accounts, which was previously missing from the documentation.

  • Adds detailed sign-in instructions for users with enterprise-managed accounts ending in .ghe
  • Provides guidance on entering enterprise/tenant names and completing SAML authentication

content/support/contacting-github-support/creating-a-support-ticket.md
* If your organization uses Data Residency or Enterprise 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.
Copy link

Copilot AI Aug 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The hardcoded text 'Data Residency' and 'Enterprise Managed Users' should use variables instead. Check data/variables/enterprise.yml for existing variables like {% data variables.enterprise.prodname_managed_user %} for managed user accounts, or define new variables if they don't exist.

Copilot uses AI. Check for mistakes.
@adamrr724 adamrr724 changed the title Fix formatting in support ticket documentation Adding .ghe support ticket creation steps Aug 8, 2025
@Sharra-writes Sharra-writes added content This issue or pull request belongs to the Docs Content team account-and-profile Content relating to account and profile and removed triage Do not begin working on this issue until triaged by the team labels Aug 11, 2025
@Sharra-writes Sharra-writes added this pull request to the merge queue Aug 12, 2025
Merged via the queue into github:main with commit 4995a86 Aug 12, 2025
40 checks passed
@github-actions
Copy link
Contributor

github-actions bot commented Aug 12, 2025

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

@Sharra-writes Sharra-writes Sharra-writes approved these changes

Assignees

No one assigned

Labels

account-and-profile Content relating to account and profile content This issue or pull request belongs to the Docs Content team

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@adamrr724 @Sharra-writes @Ebonsignori