diff --git a/.github/workflows/feedback-prompt.yml b/.github/workflows/feedback-prompt.yml index 66908c4d05e0..5cb1a6bdab99 100644 --- a/.github/workflows/feedback-prompt.yml +++ b/.github/workflows/feedback-prompt.yml @@ -53,22 +53,21 @@ jobs: .join(" "); let commentBody; - if (assignees) { commentBody = "π " + assignees + - " - Please leave us feedback on your contributing experience! " + - "To do this, please go to `#docs-contributor-feedback` on Slack."; + " - Thanks for your contribution! " + + "If you think something could be improved about the contributor experience, please post in `#docs-contributor-feedback` on Slack."; } else if (prAuthor.toLowerCase() !== "copilot") { commentBody = "π @" + prAuthor + - " - Please leave us feedback on your contributing experience! " + - "To do this, please go to `#docs-contributor-feedback` on Slack."; + " - Thanks for your contribution! " + + "If you think something could be improved about the contributor experience, please post in `#docs-contributor-feedback` on Slack."; } else { // nobody to mention! commentBody = - "π Please leave us feedback on your contributing experience! " + - "To do this, please go to `#docs-contributor-feedback` on Slack."; + "π Thanks for your contribution! " + + "If you think something could be improved about the contributor experience, please post in `#docs-contributor-feedback` on Slack."; } await github.rest.issues.createComment({ diff --git a/content/admin/managing-accounts-and-repositories/communicating-information-to-users-in-your-enterprise/configuring-custom-footers.md b/content/admin/managing-accounts-and-repositories/communicating-information-to-users-in-your-enterprise/configuring-custom-footers.md index ab9c712b129a..33ef64d70e8e 100644 --- a/content/admin/managing-accounts-and-repositories/communicating-information-to-users-in-your-enterprise/configuring-custom-footers.md +++ b/content/admin/managing-accounts-and-repositories/communicating-information-to-users-in-your-enterprise/configuring-custom-footers.md @@ -22,9 +22,7 @@ You can configure the web UI for your enterprise to display a custom footer with {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} -1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **Profile**. -1. At the top of the page, under the navigation bar, click **Custom footer**. - -  +1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **General**. +1. Navigate to **Custom footer**. 1. Under each "Footer Link" heading, type a title and URL. -1. To save the content and display the custom footer, click **Update custom footer**. +1. To save the content and display the custom footer, click **Update footer**. diff --git a/content/admin/managing-your-enterprise-account/configuring-user-display-names-for-your-enterprise.md b/content/admin/managing-your-enterprise-account/configuring-user-display-names-for-your-enterprise.md new file mode 100644 index 000000000000..7760298bce78 --- /dev/null +++ b/content/admin/managing-your-enterprise-account/configuring-user-display-names-for-your-enterprise.md @@ -0,0 +1,54 @@ +--- +title: 'Configuring user display names for your enterprise' +intro: 'You can choose whether the profile name (first and last name) of your enterprise members appear alongside their username across {% data variables.product.github %}.' +versions: + ghec: '*' + ghes: '*' +contentType: how-tos +topics: + - Accounts + - Enterprise +permissions: Enterprise and organization admins can configure whether profile names (first and last name) appear alongside usernames across {% data variables.product.github %}. +shortTitle: Configure user display names +--- + +## About user display names for enterprises + +A user display name controls how enterprise members are shown across {% data variables.product.prodname_enterprise %}. When the feature is enabled, a memberβs profile name (first and last name) appears alongside their username in places like repositories, issues, pull requests, and {% data variables.product.prodname_discussions %}. The setting applies to public, private, and internal repositories within your enterprise's organizations. + +When set at the enterprise level, this policy is applied across all organizations within your enterprise. + +Once configured, your chosen display format will be visible throughout these key areas: + +* Pull requests: reviewers, assignees, pull request authors, activities, comments, @-mentions, and commits +* Issues: assignee, comments, activities, @-mentions, and owner +* Discussions: discussion owners, comments, and @-mentions +* Projects: assignee + +By default: + +* {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_emus %} and {% data variables.product.prodname_ghe_server %} show profile names alongside usernames. +* All other enterprise accounts show usernames only. + +## Changing the user display name setting for an enterprise + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +1. On the "Manage your enterprise profile" page, go to "Member appearance". +1. Under "Profile name visibility", select one of the following options in the adjacent dropdown list. + * **Enable everywhere** to show profile names alongside usernames across all organizations in your enterprise, including in repositories, issues, pull requests, and discussions. + * **Disable everywhere** to show **usernames only** across all organizations in your enterprise. + * **Let organizations decide** to allow each organization in your enterprise to configure this setting. + +## Changing the user display name setting for an organization + +> [!NOTE] +> The organization-level setting will only be configurable if the enterprise-level policy is set to **Let organizations decide**. + +To manage configure user display name at the organization level: +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +1. On the "Manage your enterprise profile" page, go to "Member appearance". +1. Under "Profile name visibility", select one of the following options in the toggle. + * **On** to show profile names alongside usernames in your organization, including in repositories, issues, pull requests, and discussions. + * **Off** to show **usernames only** across your organization. diff --git a/content/admin/managing-your-enterprise-account/deleting-an-enterprise-account.md b/content/admin/managing-your-enterprise-account/deleting-an-enterprise-account.md index d602499c79bf..a4fd0bcbf967 100644 --- a/content/admin/managing-your-enterprise-account/deleting-an-enterprise-account.md +++ b/content/admin/managing-your-enterprise-account/deleting-an-enterprise-account.md @@ -42,7 +42,7 @@ If you upgraded to an enterprise account from a single organization and then del {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} 1. If you are not trialing {% data variables.product.prodname_ghe_cloud %}, delete your enterprise account: - 1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **Profile**. + 1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **General**. 1. In the "Danger Zone" section, click **Delete this enterprise**. 1. In the text box, type the enterprise slug to confirm the deletion, then click **Delete this enterprise**. 1. If you are trialing {% data variables.product.prodname_ghe_cloud %}, cancel your trial, or delete the expired trial: diff --git a/content/admin/managing-your-enterprise-account/index.md b/content/admin/managing-your-enterprise-account/index.md index 51cb1178acad..22b3cba1ac0b 100644 --- a/content/admin/managing-your-enterprise-account/index.md +++ b/content/admin/managing-your-enterprise-account/index.md @@ -9,6 +9,6 @@ children: - /creating-a-readme-for-an-enterprise - /deleting-an-enterprise-account - /changing-the-url-for-your-enterprise + - /configuring-user-display-names-for-your-enterprise shortTitle: Manage enterprise account --- - diff --git a/content/admin/overview/setting-up-a-trial-of-github-enterprise-cloud.md b/content/admin/overview/setting-up-a-trial-of-github-enterprise-cloud.md index 627611a7201e..133951203df6 100644 --- a/content/admin/overview/setting-up-a-trial-of-github-enterprise-cloud.md +++ b/content/admin/overview/setting-up-a-trial-of-github-enterprise-cloud.md @@ -114,7 +114,7 @@ You can cancel a trial at any time. Once the trial has expired, you can delete t {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} -1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **Profile**. +1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **General**. 1. At the bottom of the page, in the "Danger zone" section, click **Cancel trial** or **Delete trial**. ## Further reading diff --git a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies.md b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies.md index 3d586ae08480..7dc4b4802652 100644 --- a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies.md +++ b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies.md @@ -20,7 +20,7 @@ category: - Manage Copilot for a team --- -When an organization owner assigns a {% data variables.product.prodname_copilot_short %} license to a member of their organization, the availability of features and models is controlled by policies. If you are using a dedicated enterprise to manage {% data variables.copilot.copilot_business_short %} without {% data variables.product.prodname_enterprise %} licenses, see [AUTOTITLE](/copilot/how-tos/set-up/set-up-a-dedicated-enterprise-for-copilot-business). +When an organization owner assigns a {% data variables.product.prodname_copilot_short %} license to a member of their organization, the availability of features and models is controlled by policies. ## Defining policies for your enterprise diff --git a/content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md b/content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md index 1f0669adc7c7..07f243df4025 100644 --- a/content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md +++ b/content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md @@ -156,9 +156,12 @@ You can run {% data variables.copilot.copilot_coding_agent %} on self-hosted run You must configure your firewall to allow connections to the [standard hosts required for {% data variables.product.prodname_actions %} self-hosted runners](/actions/reference/runners/self-hosted-runners#accessible-domains-by-function), plus the following hosts: - * `api.githubcopilot.com` * `uploads.github.com` * `user-images.githubusercontent.com` + * `api.individual.githubcopilot.com` (if you expect {% data variables.copilot.copilot_pro_short %} or {% data variables.copilot.copilot_pro_plus_short %} users to use {% data variables.copilot.copilot_coding_agent %} in your repository) + * `api.business.githubcopilot.com` (if you expect {% data variables.copilot.copilot_business_short %} users to use {% data variables.copilot.copilot_coding_agent %} in your repository) + * `api.enterprise.githubcopilot.com` (if you expect {% data variables.copilot.copilot_enterprise_short %} users to use {% data variables.copilot.copilot_coding_agent %} in your repository) + * `api.githubcopilot.com` (*no longer required after February 27, 2026*) 1. Disable {% data variables.copilot.copilot_coding_agent %}'s integrated firewall in your repository settings. The firewall is not compatible with self-hosted runners. Unless this is disabled, use of {% data variables.copilot.copilot_coding_agent %} will be blocked. For more information, see [AUTOTITLE](/copilot/customizing-copilot/customizing-or-disabling-the-firewall-for-copilot-coding-agent). 1. In your `copilot-setup-steps.yml` file, set the `runs-on` attribute to your ARC-managed scale set name: diff --git a/src/graphql/data/fpt/changelog.json b/src/graphql/data/fpt/changelog.json index bc8c2ad61be8..3926434280d4 100644 --- a/src/graphql/data/fpt/changelog.json +++ b/src/graphql/data/fpt/changelog.json @@ -1,4 +1,23 @@ [ + { + "schemaChanges": [ + { + "title": "The GraphQL schema includes these changes:", + "changes": [] + } + ], + "previewChanges": [], + "upcomingChanges": [ + { + "title": "The following changes will be made to the schema:", + "changes": [ + "
On member Team.viewerCanSubscribe:viewerCanSubscribe will be removed. Effective 2026-07-01.
On member Team.viewerSubscription:viewerSubscription will be removed. Effective 2026-07-01.
Check if the viewer is able to change their subscription status for the repository.
", + "description": "Check if the viewer is able to change their subscription status for the subscribable entity.
", "type": "Boolean!", "id": "boolean", "kind": "scalars", - "href": "/graphql/reference/scalars#boolean" + "href": "/graphql/reference/scalars#boolean", + "isDeprecated": true, + "deprecationReason": "Team.viewerCanSubscribe will be removed. Team notifications subscriptions are being deprecated. Removal on 2026-07-01 UTC.
Team.viewerSubscription will be removed. Team notifications subscriptions are being deprecated. Removal on 2026-07-01 UTC.
viewerSubscription will be removed.
Team.viewerSubscription will be removed. Team notifications subscriptions are being deprecated.
viewerCanSubscribe will be removed.
Team.viewerCanSubscribe will be removed. Team notifications subscriptions are being deprecated.
Check if the viewer is able to change their subscription status for the repository.
", + "description": "Check if the viewer is able to change their subscription status for the subscribable entity.
", "type": "Boolean!", "id": "boolean", "kind": "scalars", - "href": "/graphql/reference/scalars#boolean" + "href": "/graphql/reference/scalars#boolean", + "isDeprecated": true, + "deprecationReason": "Team.viewerCanSubscribe will be removed. Team notifications subscriptions are being deprecated. Removal on 2026-07-01 UTC.
Team.viewerSubscription will be removed. Team notifications subscriptions are being deprecated. Removal on 2026-07-01 UTC.
viewerSubscription will be removed.
Team.viewerSubscription will be removed. Team notifications subscriptions are being deprecated.
viewerCanSubscribe will be removed.
Team.viewerCanSubscribe will be removed. Team notifications subscriptions are being deprecated.