Repo sync

content/authentication/authenticating-with-single-sign-on/authorizing-a-personal-access-token-for-use-with-single-sign-on.md

@@ -7,6 +7,7 @@ redirect_from:
   - /github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
   - /github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
   - /authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
+  - /authentication/authenticating-with-single-sign-on/authorizing-credentials-for-single-sign-on-with-a-github-app
 versions:
   ghec: '*'
 shortTitle: '{% data variables.product.pat_generic_caps %} with SSO'
@@ -19,10 +20,6 @@ You must authorize your {% data variables.product.pat_v1 %} after creation befor
 
 {% data reusables.saml.authorized-creds-info %}
 
-Enterprise administrators can use a {% data variables.product.prodname_github_app %} to authorize credentials for multiple organizations. See [AUTOTITLE](/authentication/authenticating-with-single-sign-on/authorizing-credentials-for-single-sign-on-with-a-github-app).
-
-## Authorizing a {% data variables.product.pat_v1 %}
-
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.personal_access_tokens %}

content/authentication/authenticating-with-single-sign-on/index.md

@@ -13,7 +13,6 @@ children:
   - /about-authentication-with-single-sign-on
   - /authorizing-an-ssh-key-for-use-with-single-sign-on
   - /authorizing-a-personal-access-token-for-use-with-single-sign-on
-  - /authorizing-credentials-for-single-sign-on-with-a-github-app
   - /authorizing-an-app-for-single-sign-on
   - /viewing-and-managing-your-active-sso-sessions
 shortTitle: Authenticate with SSO

content/code-security/index.md

@@ -8,7 +8,7 @@ redirect_from:
   - /enterprise-onboarding/feature-enhancements/about-code-security-for-your-enterprise
   - /enterprise-onboarding/feature-enhancements/about-enterprise-security
 introLinks:
-  overview: '{% ifversion ghes %}/code-security/getting-started/github-security-features{% endif %}'
+  overview: '/code-security/getting-started/github-security-features'
   generate_secret_risk_assessment_report_for_free: '{% ifversion secret-risk-assessment %}https://github.com/get_started?with=risk-assessment{% endif %}'
 layout: discovery-landing
 contentType: landing

content/copilot/how-tos/copilot-cli/use-copilot-cli/set-session-limit.md

@@ -27,8 +27,8 @@ These session limits are **soft limits**. If a response is in progress when the
 
 How the limit is set and applied depends on whether you are in an interactive session or running the CLI programmatically.
 
-> [!TIP]
-> {% data variables.product.prodname_ai_credit_singular %} session limits work best when set to > 30 {% data variables.product.prodname_ai_credits_short %} as most model calls will cost more than 20 {% data variables.product.prodname_ai_credits_short %}.
+> [!NOTE]
+> {% data variables.product.prodname_ai_credit_singular %} session limits must be set to at least 30 {% data variables.product.prodname_ai_credits_short %}.
 
 ### Setting a limit within an interactive session
 

content/copilot/how-tos/copilot-cli/use-copilot-cli/steer-agents.md

@@ -16,9 +16,11 @@ docsTeamMetrics:
 
 ## Steer the conversation while {% data variables.product.prodname_copilot_short %} is thinking
 
-While {% data variables.product.prodname_copilot_short %} is working on a task, you can enter a new prompt at any time. Any input you send while {% data variables.product.prodname_copilot_short %} is thinking is treated as steering and is considered in the context of the current task.
+While {% data variables.product.prodname_copilot_short %} is working on a task, you can enter a new prompt at any time. By default, a plain prompt you send while {% data variables.product.prodname_copilot_short %} is thinking is treated as steering and is considered in the context of the current task.
 
-There is no separate instruction queue. To provide additional instructions, enter another prompt while {% data variables.product.prodname_copilot_short %} is running. {% data variables.product.prodname_copilot_short %} processes each message in order as part of the active task.
+## Queue a prompt to be processed next
+
+You can also queue a message instead of steering with it, by pressing <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (or <kbd>Ctrl</kbd>+<kbd>Q</kbd>) instead of <kbd>Enter</kbd>. A queued message waits until the current task finishes, then runs as the next turn, instead of being folded into the task that's in progress. For more information about queued prompts, see [AUTOTITLE](/copilot/concepts/agents/copilot-cli/cancel-and-roll-back).
 
 Steering lets you:
 

content/pull-requests/how-tos/merge-and-close-pull-requests/troubleshooting-required-status-checks.md

@@ -50,6 +50,25 @@ Use the pull request status checks box to identify which commit must pass.
 
 See [AUTOTITLE](/rest/pulls/pulls#get-a-pull-request).
 
+## Checks from some workflow jobs are not evaluated
+
+A {% data variables.product.prodname_actions %} workflow run can report checks that do not appear in a pull request's checks section or satisfy required status checks in a branch ruleset. For checks created by workflow jobs to be evaluated for a pull request, the workflow run must be triggered by one of these events:
+
+* `push`
+* `pull_request`
+* `pull_request_review`
+* `pull_request_target`
+* `deployment`
+* `deployment_status`
+
+For example, if a workflow is triggered by `workflow_dispatch` on a pull request's head branch, checks reported by its jobs do not appear in the pull request's checks section. Even if the checks pass for the head commit, they do not satisfy a required status check in a branch ruleset.
+
+Check the event that triggered the workflow run. If the workflow uses another event, update its `on` configuration to use an eligible event appropriate for your workflow, such as `pull_request`. See [AUTOTITLE](/actions/reference/workflows-and-actions/events-that-trigger-workflows).
+
+This restriction applies only to checks created by workflow jobs, not to checks created by an external {% data variables.product.prodname_github_app %}.
+
+Merge queues require the separate `merge_group` event. See [Status checks with {% data variables.product.prodname_actions %} and a Merge queue](#status-checks-with-github-actions-and-a-merge-queue).
+
 ## Handling skipped but required checks
 
 | Cause | Result | How to fix or check |

data/reusables/enterprise-accounts/enterprise-apps-capabilities.md

@@ -7,9 +7,6 @@ Enterprise-installed {% data variables.product.prodname_github_apps %} cannot ca
 {%- ifversion enterprise-billing-github-app %}
 * Manage enterprise billing, including budgets, cost centers, and usage reports. For more information, see [AUTOTITLE](/rest/billing).
 {%- endif %}
-{%- ifversion ghec %}
-* Authorize {% data variables.product.pat_v1_plural %} and verified, user-owned SSH authentication keys for SSO in selected organizations. See [AUTOTITLE](/authentication/authenticating-with-single-sign-on/authorizing-credentials-for-single-sign-on-with-a-github-app).
-{%- endif %}
 * Call the enterprise SCIM APIs
 
 Check the [changelog](https://github.blog/changelog/) for updates on new APIs and permissions for {% data variables.product.prodname_github_apps %}.