Merge pull request #40441 from github/repo-sync

Repo sync

Author: docs-bot

CHANGELOG.md

@@ -2,6 +2,16 @@
 
 **17 September 2025**
 
+We added documentation for expanded features for reusing workflow configurations in GitHub Actions. 
+
+You can now use YAML anchors and aliases to reuse pieces of content in a workflow. See [YAML anchors and aliases](https://docs.github.com/en/actions/concepts/workflows-and-actions/reusing-workflow-configurations#yaml-anchors-and-aliases). 
+
+To keep the content focused on users' job-to-be-done, we simplified the procedures for [creating workflow templates for your organization](https://docs.github.com/en/actions/how-tos/reuse-automations/create-workflow-templates). In addition, we updated reference documentation for workflow templates with details on permissions, repository visibility rules, rules for the metadata file, and examples. See [Workflow templates](https://docs.github.com/en/actions/reference/workflows-and-actions/reusing-workflow-configurations#workflow-templates).
+
+<hr>
+
+**17 September 2025**
+
 You can now publish your Spark app as "read-only." 
 
 By default, data stored in Spark is shared across all users of the app. You can choose to publish your app as "read-only" if you want to showcase your app to others, but you don't want others to be able to edit or delete any stored data.

content/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/index.md

@@ -19,7 +19,9 @@ children:
   - /managing-security-and-analysis-features
   - /managing-your-tab-size-rendering-preference
   - /permission-levels-for-a-project-board-owned-by-a-personal-account
+  - /manage-cookie-preferences
   - /managing-accessibility-settings
+  - /prepare-for-job-change
   - /managing-access-to-your-personal-accounts-project-boards
   - /integrating-jira-with-your-personal-projects
   - /set-your-hiring-status

…or-githubs-enterprise-marketing-pages.md …nt-settings/manage-cookie-preferences.mdcontent/account-and-profile/tutorials/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages.md renamed to content/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/manage-cookie-preferences.md content/account-and-profile/tutorials/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages.md renamed to content/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/manage-cookie-preferences.md

@@ -1,6 +1,6 @@
 ---
-title: Managing your cookie preferences for GitHub's enterprise marketing pages
-intro: 'You can control how {% data variables.product.company_short %} uses information from non-essential tracking cookies for enterprise marketing pages.'
+title: Manage cookie preferences
+intro: You can control how {% data variables.product.company_short %} uses information from non-essential tracking cookies for enterprise marketing pages.
 versions:
   fpt: '*'
   ghes: '*'
@@ -11,15 +11,13 @@ shortTitle: Manage cookie preferences
 redirect_from:
   - /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages
   - /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages
+  - /account-and-profile/tutorials/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages
+contentType: how-tos
 ---
 
-## About cookie preferences on enterprise marketing pages
-
-{% data variables.product.company_short %} may use non-essential cookies on some enterprise marketing pages. You can customize how these cookies behave. For more information about how {% data variables.product.company_short %} uses cookies, see [AUTOTITLE](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement).
-
 ## Changing your cookie preferences
 
-You can customize how non-essential cookies behave on any {% data variables.product.company_short %} enterprise marketing page.
+You can customize how non-essential cookies behave on any {% data variables.product.company_short %} enterprise marketing page.  For more information about how {% data variables.product.company_short %} uses cookies, see [AUTOTITLE](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement).
 
 1. Navigate to the {% data variables.product.company_short %} enterprise marketing page where you'd like to change your cookie preferences. For example, navigate to [{% data variables.product.company_short %} Resources](https://resources.github.com/).
 1. Scroll to the bottom of the page, then click **Manage Cookies**.

content/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/prepare-for-job-change.md

@@ -0,0 +1,88 @@
+---
+title: Prepare for job change
+intro: If you use your {% data variables.product.github %} account for both personal and work purposes, there are steps to follow when you leave your company or organization.
+redirect_from:
+  - /articles/best-practices-for-leaving-your-company
+  - /github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company
+  - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company
+  - /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company
+  - /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company
+  - /account-and-profile/reference/best-practices-for-leaving-your-company
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: Prepare for job change
+contentType: how-tos
+---
+
+## Update your personal account information
+
+1. Unverify your company email address by deleting it in your Email settings.
+  
+   After removal, you can re-add this email without verifying to keep any associated commits linked to your account.
+  
+   For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address).
+
+1. Change your primary email address from your company email to your personal email.
+  
+   For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address).
+
+1. Verify your new primary email address.
+  
+   For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/verifying-your-email-address).
+
+1. Update your {% data variables.product.github %} username if it contains references to your company or organization.
+  
+   For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/changing-your-github-username).
+
+1. Review and update your two-factor authentication (2FA) methods to ensure they aren't linked to company resources:
+
+   * If you use a TOTP app on a company phone, transfer it to your personal device.
+   * If you've registered company-owned security keys, remove them and add personal ones instead.
+   * If you're using {% data variables.product.prodname_mobile %} on a company device, install it on your personal device.
+   * Download fresh recovery codes and store them in a personal secure location.
+
+   For more information, see [AUTOTITLE](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication).
+
+## Leave organization memberships
+
+> [!NOTE] Unless you're using a {% data variables.enterprise.prodname_managed_user %}, you'll still be able to access your personal account after leaving an organization.
+
+1. If you're the organization owner, transfer ownership to another person before removing yourself.
+  
+   For more information, see [AUTOTITLE](/organizations/managing-organization-settings/transferring-organization-ownership).
+
+1. Remove yourself from the organization.
+  
+   For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization).
+
+## Clean up professional repository associations
+
+1. Remove yourself as a collaborator from repositories owned by others.
+  
+   For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository).
+
+1. Stop watching work-related repositories to avoid unnecessary notifications.
+  
+   To manage your watched repositories, visit https://github.com/watching.
+
+1. Transfer repositories that you own that others may need to continue working on.
+  
+   For more information, see [AUTOTITLE](/repositories/creating-and-managing-repositories/transferring-a-repository).
+
+1. Delete any work-related forks that belong to you.
+  
+   Deleting a fork doesn't delete the upstream repository.
+  
+   For more information, see [AUTOTITLE](/repositories/creating-and-managing-repositories/deleting-a-repository).
+
+1. Delete local copies of your work repositories from your computer by running the following command:
+
+   ```shell
+   rm -rf WORK_DIRECTORY
+   ```
+  
+   Replace `WORK_DIRECTORY` with the path to your work repository.

content/account-and-profile/reference/best-practices-for-leaving-your-company.md

@@ -11,7 +11,6 @@ children:
   - /personal-dashboard
   - /permission-levels-for-a-personal-account-repository
   - /profile-contributions-reference
-  - /best-practices-for-leaving-your-company
   - /types-of-emails-github-sends
   - /email-addresses-reference
   - /personal-account-reference

content/account-and-profile/reference/index.md

@@ -11,7 +11,6 @@ topics:
   - Profiles
 children:
   - /personalize-your-profile
-  - /managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages
   - /using-your-github-profile-to-enhance-your-resume
 ---
 

content/account-and-profile/tutorials/index.md

@@ -12,6 +12,7 @@ children:
   - /track-copilot-sessions
   - /review-copilot-prs
   - /extend-coding-agent-with-mcp
+  - /integrate-coding-agent-with-teams
   - /customize-the-agent-environment
   - /customize-the-agent-firewall
   - /troubleshoot-coding-agent

content/copilot/how-tos/use-copilot-agents/coding-agent/index.md

@@ -0,0 +1,65 @@
+---
+title: Integrating Copilot coding agent with Teams
+shortTitle: Integrate coding agent with Teams
+intro: 'You can use the {% data variables.product.github %} integration in Teams to provide context and open pull requests all from within your Teams channels.'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+contentType: how-tos
+---
+
+> [!NOTE]
+> This feature is currently in {% data variables.release-phases.public_preview %} and subject to change.
+
+The {% data variables.product.github %} integration in Microsoft Teams allows you to interact with {% data variables.copilot.copilot_coding_agent %} all from within your Teams channels. From within a Teams thread you can initiate {% data variables.copilot.copilot_coding_agent_short %} sessions and open pull requests, using the context of your conversation.
+
+> [!NOTE]
+> When you mention @{% data variables.product.github %} in a Teams thread, the agent will capture the entire thread as context for your request, understanding and implementing solutions based on the discussion. This context is stored in the pull request.
+
+## Prerequisites
+
+* You must have a {% data variables.product.github %} account with access to {% data variables.product.prodname_copilot_short %} through {% data variables.copilot.copilot_pro_short %}, {% data variables.copilot.copilot_pro_plus_short %}, {% data variables.copilot.copilot_business_short %}, or {% data variables.copilot.copilot_enterprise_short %}.
+* You must have a Teams account and be a member of a channel.
+
+## Installing the {% data variables.product.github %} app in Teams
+
+The {% data variables.product.github %} app only needs to be installed once in a team. After the app is installed, any member of the team can connect their {% data variables.product.github %} account to the app and start using it.
+
+1. Open the [{% data variables.product.github %} integration installation link](https://teams.microsoft.com/l/app/836ecc9e-6dca-4696-a2e9-15e252cd3f31) in your web browser to launch Teams and the installation dialog.
+1. Click **Add** to add the app to your team.
+1. Follow the prompts on screen to authenticate and authorize the app.
+
+## Connecting the {% data variables.product.github %} app to your {% data variables.product.github %} account
+
+The first time you use the {% data variables.product.github %} app in Teams, you need to connect it to your {% data variables.product.github %} account and set a default repository. The default repository provides the context that {% data variables.product.prodname_copilot_short %} uses when responding to prompts, and it’s also where pull requests created by {% data variables.copilot.copilot_coding_agent %} sessions will be opened unless you specify a repository in your prompt.
+
+To get started, mention `@{% data variables.product.github %} <YOUR_TASK>` in any Teams thread. The app will guide you through signing in and setting a default repository. Or you can connect your {% data variables.product.github %} account and set the default repository manually by following these steps:
+
+1. In Teams, mention the app in a thread by typing `@{% data variables.product.github %}`.
+1. Click **signin** from the list of suggestions.
+1. Follow the prompts to sign in to your {% data variables.product.github %} account.
+1. In the thread, mention the app by typing `@{% data variables.product.github %}`.
+1. Click **settings** to set the default repository.
+
+## Using the {% data variables.product.prodname_copilot_short %} app in Teams
+
+You can interact with the {% data variables.product.github %} app in Teams by mentioning it in a thread. The agent will respond to your messages and perform tasks based on your requests. Only users with **write** access to the default repository—or the repository specified in their prompt—can trigger {% data variables.copilot.copilot_coding_agent %} to work. Contributors to the thread without **write** access can help guide {% data variables.product.prodname_copilot_short %} by providing input to the conversation, which will be used as context when making changes in the pull request.
+
+1. In Teams, mention the app in a thread by typing @{% data variables.product.github %}.
+1. Type your message or request, then send it. Optionally, you can specify a repository or branch using the following syntax:
+
+    ```text
+    @GitHub Add "Hello World" to the README in repo=REPO_OWNER/REPO_NAME branch=BRANCH_NAME
+    ```
+
+   The `repo` parameter tells {% data variables.copilot.copilot_coding_agent %} which repository to use for the request, and the `branch` parameter specifies an existing branch of the repository that should be used as the base branch for a pull request. By default, {% data variables.product.prodname_copilot_short %} uses your configured default repository and the repository’s default branch.
+  
+   {% data variables.product.prodname_copilot_short %} will initiate a {% data variables.copilot.copilot_coding_agent_short %} session and respond with a summary of the changes it plans to make, including a link to the pull request it has created in the repository.
+
+You can continue to iterate on the pull request in the same Teams thread. Mention @{% data variables.product.github %} with your suggested change, and the {% data variables.copilot.copilot_coding_agent %} will use all of the messages in the thread since the previous mention to iterate on the existing pull request.
+
+## Further reading
+
+* [AUTOTITLE](/copilot/concepts/coding-agent/coding-agent)
+* [AUTOTITLE](/copilot/concepts/coding-agent/enable-coding-agent)