Repo sync

.github/workflows/needs-sme-stale-check.yaml

@@ -19,7 +19,7 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/stale@3a9db7e6a41a89f618792c92c0e97cc736e1b13f # v10.0.0
+      - uses: actions/stale@4391f3da665fdf50b6810c1a66712fb9ba21aa93 # v11.0.0
         id: stale
         with:
           only-labels: needs SME

.github/workflows/no-response.yaml

@@ -33,7 +33,7 @@ jobs:
       github.actor != 'github-actions' &&
       !endsWith(github.actor, '[bot]')
     steps:
-      - uses: actions/stale@3a9db7e6a41a89f618792c92c0e97cc736e1b13f # v10.0.0
+      - uses: actions/stale@4391f3da665fdf50b6810c1a66712fb9ba21aa93 # v11.0.0
         id: stale
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/stale.yml

@@ -21,7 +21,7 @@ jobs:
     if: github.repository == 'github/docs-internal'
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/stale@3a9db7e6a41a89f618792c92c0e97cc736e1b13f # v10.0.0
+      - uses: actions/stale@4391f3da665fdf50b6810c1a66712fb9ba21aa93 # v11.0.0
         id: stale
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/triage-stale-check.yml

@@ -21,7 +21,7 @@ jobs:
       pull-requests: write
 
     steps:
-      - uses: actions/stale@3a9db7e6a41a89f618792c92c0e97cc736e1b13f # v10.0.0
+      - uses: actions/stale@4391f3da665fdf50b6810c1a66712fb9ba21aa93 # v11.0.0
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
           days-before-stale: 30
@@ -60,7 +60,7 @@ jobs:
       issues: write
       pull-requests: write
     steps:
-      - uses: actions/stale@3a9db7e6a41a89f618792c92c0e97cc736e1b13f # v10.0.0
+      - uses: actions/stale@4391f3da665fdf50b6810c1a66712fb9ba21aa93 # v11.0.0
         id: stale
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}

content/actions/concepts/workflows-and-actions/reusing-workflow-configurations.md

@@ -20,6 +20,12 @@ contentType: concepts
 
 Rather than copying and pasting from one workflow to another, you can make workflows reusable. You and anyone with access to the reusable workflow can then call the reusable workflow from another workflow.
 
+{% ifversion copilot %}
+
+Reusable workflows also complement {% data variables.copilot.agentic_workflows_short %}: an agentic workflow can call approved, deterministic reusable workflows rather than duplicating logic. For more information, see [AUTOTITLE](/copilot/how-tos/github-agentic-workflows/creating-github-agentic-workflows).
+
+{% endif %}
+
 Reusing workflows avoids duplication. This makes workflows easier to maintain and allows you to create new workflows more quickly by building on the work of others, just as you do with actions. Workflow reuse also promotes best practice by helping you to use workflows that are well designed, have already been tested, and have been proven to be effective. Your organization can build up a library of reusable workflows that can be centrally maintained.
 
 The diagram below shows an in-progress workflow run that uses a reusable workflow.
@@ -77,6 +83,12 @@ If you use a commit SHA when referencing the reusable workflow, you can ensure t
 
 For more information, see [AUTOTITLE](/actions/how-tos/reuse-automations/create-workflow-templates).
 
+{% ifversion copilot %}
+
+Organizations can also share and govern approved {% data variables.copilot.agentic_workflows_short %} templates alongside shared actions and reusable workflows. To create templates with {% data variables.copilot.github_agentic_workflows %}, see [AUTOTITLE](/copilot/how-tos/github-agentic-workflows/creating-github-agentic-workflows).
+
+{% endif %}
+
 {% ifversion fpt or ghec %}
 
 ## YAML anchors and aliases

content/actions/get-started/continuous-deployment.md

@@ -34,6 +34,13 @@ You can configure your CD workflow to run when an event occurs (for example, whe
 
 {% data variables.product.prodname_actions %} provides features that give you more control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. You can use concurrency to limit your CD pipeline to a maximum of one in-progress deployment{% ifversion actions-nga %}{% else %} and one pending deployment{% endif %}. For more information about these features, see [AUTOTITLE](/actions/how-tos/deploy/configure-and-manage-deployments/control-deployments) and [AUTOTITLE](/actions/how-tos/deploy/configure-and-manage-deployments/manage-environments).
 
+{% ifversion copilot %}
+
+> [!TIP]
+> You can use {% data variables.copilot.agentic_workflows_short %} for deployment preparation, such as release notes, change analysis, and rollout summaries, while keeping production deployments in deterministic {% data variables.product.prodname_actions %} workflows. For more information, see [AUTOTITLE](/copilot/how-tos/github-agentic-workflows/creating-github-agentic-workflows).
+
+{% endif %}
+
 ## Workflow templates and third-party actions
 
 {% data reusables.actions.cd-templates-actions %}

content/actions/get-started/understand-github-actions.md

@@ -114,6 +114,13 @@ For more information{% ifversion fpt or ghec %} about self-hosted runners{% endi
 
 {% data reusables.actions.onboarding-next-steps %}
 
+{% ifversion copilot %}
+
+> [!NOTE]
+> For automations that require contextual judgment about your repository's content, you can also author {% data variables.copilot.agentic_workflows_short %} in natural language instead of a traditional {% data variables.product.prodname_actions %} workflow. For more information, see [AUTOTITLE](/copilot/how-tos/github-agentic-workflows/quickstart) and [AUTOTITLE](/copilot/how-tos/github-agentic-workflows/creating-github-agentic-workflows).
+
+{% endif %}
+
 {% ifversion ghec or ghes %}
 
 ## Further reading

content/actions/how-tos/manage-workflow-runs/manually-run-a-workflow.md

@@ -93,3 +93,4 @@ When using the REST API, you configure the `inputs` and `ref` as request body pa
 > You can define up to {% ifversion fpt or ghec %}25 {% else %}10 {% endif %} `inputs` for a `workflow_dispatch` event.
 
 For more information about using the REST API, see [AUTOTITLE](/rest/actions/workflows#create-a-workflow-dispatch-event).
+

content/actions/reference/workflows-and-actions/events-that-trigger-workflows.md

@@ -27,6 +27,12 @@ Some events have multiple activity types. For these events, you can specify whic
 > [!NOTE]
 > Not all webhook events trigger workflows.
 
+{% ifversion copilot %}
+
+Like {% data variables.product.prodname_actions %} workflows, {% data variables.copilot.agentic_workflows_short %} can be triggered by repository events and schedules. For an example, see [AUTOTITLE](/copilot/how-tos/github-agentic-workflows/creating-github-agentic-workflows).
+
+{% endif %}
+
 ## `branch_protection_rule`
 
 | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
@@ -376,7 +382,7 @@ on:
 > * {% data reusables.developer-site.multiple_activity_types %} Although only the `checks_requested` activity type is supported, specifying the activity type will keep your workflow specific if more activity types are added in the future. For information about each activity type, see [AUTOTITLE](/webhooks/webhook-events-and-payloads#merge_group). {% data reusables.developer-site.limit_workflow_to_activity_types %}
 > * {% data reusables.actions.merge-group-event-with-required-checks %}
 
-Runs your workflow when a pull request is added to a merge queue, which adds the pull request to a merge group. For more information see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue).
+Runs your workflow when a pull request is added to a merge queue, which adds the pull request to a merge group. For more information see [AUTOTITLE](/pull-requests/how-tos/merge-and-close-pull-requests/merging-a-pull-request-with-a-merge-queue).
 
 For example, you can run a workflow when the `checks_requested` activity has occurred.
 
@@ -461,7 +467,7 @@ on:
 
 Runs your workflow when activity on a pull request in the workflow's repository occurs. For example, if no activity types are specified, the workflow runs when a pull request is opened or reopened or when the head branch of the pull request is updated. For activity related to pull request reviews, pull request review comments, or pull request comments, use the [`pull_request_review`](#pull_request_review), [`pull_request_review_comment`](#pull_request_review_comment), or [`issue_comment`](#issue_comment) events instead. For information about the pull request APIs, see [AUTOTITLE](/graphql/reference/pulls#object-pullrequest) in the GraphQL API documentation or [AUTOTITLE](/rest/pulls).
 
-Note that `GITHUB_SHA` for this event is the last merge commit of the pull request merge branch. If you want to get the commit ID for the last commit to the head branch of the pull request, use `github.event.pull_request.head.sha` instead. For more information about merge branches, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests#pull-request-refs-and-merge-branches).
+Note that `GITHUB_SHA` for this event is the last merge commit of the pull request merge branch. If you want to get the commit ID for the last commit to the head branch of the pull request, use `github.event.pull_request.head.sha` instead. For more information about merge branches, see [AUTOTITLE](/pull-requests/reference/pull-requests#pull-request-refs-and-merge-branches).
 
 ### How the merge branch affects your workflow
 
@@ -1272,3 +1278,5 @@ jobs:
               body: 'Thank you for the PR!'
             });
 ```
+
+

content/actions/reference/workflows-and-actions/reusing-workflow-configurations.md

@@ -16,8 +16,13 @@ contentType: reference
 
 ## Reusable workflows
 
-Reference information for reusable workflows.
+This article provides reference information for reusable workflows and workflow templates, including access rules, limitations, supported keywords, and runner behavior.
 
+{% ifversion copilot %}
+
+You can centralize deterministic, repeatable logic in reusable workflows, and use {% data variables.copilot.agentic_workflows_short %} for tasks that require contextual judgment about your repository's content such as analysis, summaries, and recommendations. For more information, see [AUTOTITLE](/copilot/how-tos/github-agentic-workflows/creating-github-agentic-workflows).
+
+{% endif %}
 ### Access to reusable workflows
 
 A reusable workflow can be used by another workflow if any of the following is true:
@@ -244,3 +249,4 @@ jobs:
 ```
 
 {% endif %}
+

content/actions/reference/workflows-and-actions/workflow-syntax.md

@@ -28,6 +28,12 @@ Workflow files use YAML syntax, and must have either a `.yml` or `.yaml` file ex
 
 You must store workflow files in the `.github/workflows` directory of your repository.
 
+{% ifversion copilot %}
+
+> [!TIP]
+> Unlike traditional {% data variables.product.prodname_actions %} workflows that require you to script every decision as YAML job steps, {% data variables.copilot.github_agentic_workflows %} use YAML frontmatter for triggers and configuration, but let you describe what you want in natural-language Markdown—so you don't need to anticipate and encode every scenario in advance. For more information, see [AUTOTITLE](/copilot/how-tos/github-agentic-workflows/creating-github-agentic-workflows).
+
+{% endif %}
 ## `name`
 
 {% data reusables.actions.workflows.workflow-syntax-name %}
@@ -1566,3 +1572,5 @@ Path patterns must match the whole path, and start from the repository's root.
 | `'**/migrate-*.sql'`                                | A file with the prefix `migrate-` and suffix `.sql` anywhere in the repository.                                                                                                               | `migrate-10909.sql`<br/><br/>`db/migrate-v1.0.sql`<br/><br/>`db/sept/migrate-v1.sql`    |
 | `'*.md'`<br/><br/>`'!README.md'`                    | Using an exclamation mark (`!`) in front of a pattern negates it. When a file matches a pattern and also matches a negative pattern defined later in the file, the file will not be included. | `hello.md`<br/><br/>_Does not match_<br/><br/>`README.md`<br/><br/>`docs/hello.md`      |
 | `'*.md'`<br/><br/>`'!README.md'`<br/><br/>`README*` | Patterns are checked sequentially. A pattern that negates a previous pattern will re-include file paths.                                                                                      | `hello.md`<br/><br/>`README.md`<br/><br/>`README.doc`                                   |
+
+

content/enterprise-onboarding/getting-started-with-your-enterprise/adding-users-to-your-enterprise.md → content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/add-users.md

@@ -1,14 +1,20 @@
 ---
 title: Adding users to your enterprise
 shortTitle: Add users
-intro: 'Add users to your enterprise and control access to your organization''s resources.'
+intro: You can add people directly to your enterprise.
+permissions: Enterprise owners
 versions:
   ghec: '*'
+contentType: other
+category:
+  - Manage accounts and repositories
+docsTeamMetrics:
+  - enterprise-onboarding
 redirect_from:
+  - /admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/invite-users-directly
   - /enterprise-onboarding/getting-started-with-your-enterprise/securing-enterprise-resources-with-single-sign-on
   - /enterprise-onboarding/getting-started-with-your-enterprise/securing-your-enterprise-with-managed-users
-docsTeamMetrics:
-  - enterprise-onboarding
+  - /enterprise-onboarding/getting-started-with-your-enterprise/adding-users-to-your-enterprise
 ---
 
 The method of adding users to your enterprise and controlling authentication varies depending on the enterprise type that you chose.
@@ -17,9 +23,14 @@ The method of adding users to your enterprise and controlling authentication var
 
 If you chose an enterprise with personal accounts, you will invite users to your enterprise with their existing {% data variables.product.github %} account.
 
-{% data reusables.enterprise-onboarding.inviting-users-to-your-enterprise %}
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.people-tab %}
+1. On the "Members" page, click **Invite member**.
+1. Search for the users you want to invite, then click **Invite**.
 
-Later in this onboarding journey, you will add users to teams to grant access to organizations and delegate administrative roles.
+After you invite someone to join the enterprise account, they must accept the emailed invitation before they can access the enterprise account. Pending invitations will expire after 7 days.
+
+Users will join the enterprise as unaffiliated users. You can then add users to organizations or enterprise teams and assign {% data variables.product.prodname_copilot_short %} licenses to them. For more information about unaffiliated users, see [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/abilities-of-roles#unaffiliated-users).
 
 ### Enabling single sign-on for personal accounts
 
@@ -48,7 +59,3 @@ To use {% data variables.product.prodname_emus %}, you will:
 * Provision users to your enterprise
 
 To get started, see [AUTOTITLE](/enterprise-cloud@latest/admin/managing-iam/understanding-iam-for-enterprises/getting-started-with-enterprise-managed-users).
-
-## Next steps
-
-Learn about how billing will work when your trial ends. See [AUTOTITLE](/billing/concepts/enterprise-billing/billing-for-enterprises).

content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/index.md

@@ -17,7 +17,7 @@ versions:
 children:
   - /best-practices-for-user-security
   - /create-enterprise-teams
-  - /invite-users-directly
+  - /add-users
   - /inviting-people-to-manage-your-enterprise
   - /managing-invitations-to-organizations-within-your-enterprise
   - /about-reserved-usernames-for-github-enterprise-server

content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md

@@ -25,6 +25,8 @@ Enterprise owners and billing managers automatically have a support entitlement.
 > * If the user does not have a support entitlement, their ticket will still be addressed by our Enterprise Support team, but without Premium Support features such as priority selection and guaranteed Premium SLAs.
 >
 > If a user is unsure of their entitlement status, they can contact their organization's Enterprise Support administrator.
+>
+Support entitlements do not provide a user with rights above those granted by the role of their account in the enterprise. Additional approval from an enterprise owner will still be required where the user's enterprise role does not permit the sharing of information in a support ticket.
 
 ## Adding a support entitlement to an enterprise member
 

content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md

@@ -29,3 +29,20 @@ After changing your password, you should perform these actions to make sure that
 * Make sure that no new deploy keys were created. This could enable outside servers access to your projects. For more information, see [AUTOTITLE](/authentication/connecting-to-github-with-ssh/managing-deploy-keys#deploy-keys).
 * Review recent commits made to your repositories.
 * Review the list of collaborators for each repository.
+
+{% ifversion fpt or ghec %}
+## Troubleshooting
+
+### Account is restricted after suspected compromise
+
+If {% data variables.product.github %} detects suspicious activity, your personal account may be temporarily restricted while you can still sign in. During this time, your profile URL, contribution graph, search visibility, or sensitive account actions may be unavailable. Alternatively, we may suspend the account for security reasons. If you’re unable to access your account at all, please contact {% data variables.contact.github_support %}.
+
+If you see restrictions on your account, complete the following steps to secure your account:
+
+1. Change your {% data variables.product.github %} password. For more information, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials#changing-an-existing-password).
+1. Review your security settings and remove unfamiliar apps, keys, and other credentials.
+1. Secure the email account associated with {% data variables.product.github %} and make sure you can access it.
+1. Check your inbox (and spam folder) for security emails from {% data variables.product.github %} and follow any instructions.
+
+If restrictions remain after you secure your account, contact {% data variables.contact.github_support %}.
+{% endif %}