Repo sync

content/account-and-profile/how-tos/account-management/creating-an-account-on-github.md

@@ -41,12 +41,25 @@ Later, you can explore the different types of accounts that {% data variables.pr
 1. Alternatively, click on **Continue with Google** to sign up using social login.
 1. Follow the prompts to create your personal account.
 
-During sign up, you'll be asked to verify your email address. Without a verified email address, you won't be able to complete some basic {% data variables.product.github %} tasks, such as creating a repository.
+During sign up, you'll be asked to verify your email address.
 
 Some enterprises create {% data variables.enterprise.prodname_managed_users %} for their users. You can't sign up for a personal account with an email address that's already verified for a {% data variables.enterprise.prodname_managed_user %}.
 
 {% ifversion fpt or ghec %}If you're having problems verifying your email address, there are some troubleshooting steps you can take. For more information, see [AUTOTITLE](/account-and-profile/how-tos/email-preferences/troubleshooting-email-verification).{% endif %}
 
+### Troubleshooting signup errors
+
+If you see `This email can't be used` or `We couldn't create your account` try the following:
+
+1. Use a different browser, or clear your browser's cookies and cache.
+1. Disable your browser extensions.
+1. Sign up on a different device and network.
+1. Wait a while, then try again.
+
+If you see `This email can't be used`, try a different email address or email domain. After you create your account, you can add or change email addresses. See [AUTOTITLE](/account-and-profile/how-tos/email-preferences/changing-your-primary-email-address).
+
+These suggestions may not resolve the issue. {% data variables.contact.github_support %} can't investigate individual account verification failures during signup.
+
 ## Next steps
 
 We strongly recommend that you configure 2FA for your account. 2FA is an extra layer of security that can help keep your account secure. For more information, see [AUTOTITLE](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication).

content/actions/how-tos/manage-runners/use-actions-runner-controller/deploy-runner-scale-sets.md

@@ -664,6 +664,10 @@ To customize the spec, comment out or remove `containerMode`, and append the con
 #### Example: running `dind-rootless`
 
 Before deciding to run `dind-rootless`, make sure you are aware of [known limitations](https://docs.docker.com/engine/security/rootless/#known-limitations).
+
+> [!WARNING]
+> On Kubernetes nodes running Ubuntu 24.04 and later, restrictions on unprivileged user namespaces can prevent RootlessKit from starting the Docker daemon in the `dind` container. Before using this configuration, see [Troubleshooting](https://docs.docker.com/engine/security/rootless/troubleshoot/#distribution-specific-hint) in the Docker documentation and review the Ubuntu-specific guidance with your cluster administrator.
+
 {% ifversion not ghes %}
 
 For versions of Kubernetes >= v1.29, sidecar container will be used to run docker daemon.

content/admin/monitoring-and-managing-your-instance/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md

@@ -95,18 +95,6 @@ Ensure the appliance is in maintenance mode and no background jobs are running:
    df -h /data/user
    ```
 
-## Increasing the root partition size using a new appliance
-
-1. Set up a new {% data variables.product.prodname_ghe_server %} instance with a larger root disk using the same version as your current appliance. For more information, see [AUTOTITLE](/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance).
-1. Shut down the current appliance:
-
-   ```shell
-   sudo poweroff
-   ```
-
-1. Detach the data disk from the current appliance using your virtualization platform's tools.
-1. Attach the data disk to the new appliance with the larger root disk.
-
 ## Increasing the root partition size using an existing appliance
 
 > [!WARNING]
@@ -217,3 +205,7 @@ If your appliance is configured for high-availability or geo-replication, rememb
 1. Ensure system services are functioning correctly, then release maintenance mode. For more information, see [AUTOTITLE](/admin/administering-your-instance/configuring-maintenance-mode/enabling-and-scheduling-maintenance-mode).
 
 If your appliance is configured for high-availability or geo-replication, remember to start replication on each replica node using `ghe-repl-start` after the storage on all nodes has been upgraded.
+
+## Increasing the root partition size using a new appliance
+
+To move your existing data disk to a new appliance with a larger root disk, contact GitHub Support before proceeding. Cluster and replication configuration, SSH and network configuration, and node identity stored on the root disk require additional handling, particularly for high availability, geo-replication, and clustered deployments.

content/authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md

@@ -36,7 +36,6 @@ If your country or region is not on this list, then we aren't currently able to
 <li>Brunei</li>
 <li>Bulgaria</li>
 <li>Burundi</li>
-<li>Cambodia</li>
 <li>Canada</li>
 <li>Cape Verde</li>
 <li>Cayman Islands</li>
@@ -57,7 +56,6 @@ If your country or region is not on this list, then we aren't currently able to
 <li>Gambia</li>
 <li>Georgia</li>
 <li>Germany</li>
-<li>Ghana</li>
 <li>Gibraltar</li>
 <li>Greece</li>
 <li>Guatemala</li>

content/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/managing-your-github-advanced-security-license-usage.md

@@ -42,8 +42,12 @@ Before you can effectively manage your paid use of {% data variables.product.pro
 
 The simplest way to turn off all {% data variables.product.prodname_cs_or_sp %} features for one or more repositories is to create a security configuration where the product is disabled at the top level. You can apply this custom configuration to repositories where you want to turn off paid features.
 
-> [!TIP]
-> Ensure that you give your custom configuration a very clear name, for example: "No Code Security" or "Secret Protection and Supply chain only" to avoid confusion.
+To keep {% data variables.product.prodname_code_security %} disabled, set "Default setup" and "Prevent direct alert dismissals" in the "Code scanning" section to **Disabled**. You can leave "Dependency graph" and "{% data variables.product.prodname_dependabot_alerts %}" enabled because they are included in all plans.
+
+> [!WARNING]
+> Changing "Prevent direct alert dismissals" in the "Code scanning" section to **Not set** automatically switches {% data variables.product.prodname_code_security %} to **Enabled**. To avoid unintentionally enabling paid features, organization administrators must keep "Default setup" and "Prevent direct alert dismissals" in this section **Disabled** and recheck the top-level {% data variables.product.prodname_code_security %} setting before saving and applying the configuration.
+
+Ensure that you give your custom configuration a very clear name, for example: "No Code Security" or "Secret Protection and Supply chain only" to avoid confusion.
 
 For more information, see [AUTOTITLE](/code-security/how-tos/secure-at-scale/configure-organization-security/establish-complete-coverage/create-custom-configuration) and [AUTOTITLE](/code-security/how-tos/secure-at-scale/configure-organization-security/establish-complete-coverage/apply-custom-configuration).
 

content/copilot/concepts/billing-and-usage/copilot-usage-metrics/index.md

@@ -20,6 +20,7 @@ children:
   - /content/copilot/reference/copilot-usage-metrics/lines-of-code-metrics
   - /content/copilot/reference/copilot-usage-metrics/team-level-metrics
   - /content/copilot/tutorials/roll-out-at-scale/measure-success
+  - /content/copilot/tutorials/roll-out-at-scale/communicate-copilot-impact
   - /content/copilot/tutorials/roll-out-at-scale/assign-licenses/track-usage-and-adoption
   - /content/copilot/reference/copilot-usage-metrics/example-schema
 includedCategories:

content/copilot/how-tos/copilot-on-github/chat-with-copilot/chat-in-mobile.md

@@ -22,10 +22,9 @@ category:
 
 ## Limitations
 
-The following limitations apply to {% data variables.copilot.copilot_mobile_short %}:
+If you're a member of an organization or enterprise, your access to {% data variables.copilot.copilot_mobile_short %} may depend on policies set by your administrator. See [AUTOTITLE](/copilot/concepts/enterprise/policies).
 
-* If you're a member of an organization or enterprise, your access to {% data variables.copilot.copilot_mobile_short %} may depend on policies set by your administrator. See [AUTOTITLE](/copilot/concepts/enterprise/policies).
-* If you purchased {% data variables.copilot.copilot_pro_short %}, {% data variables.copilot.copilot_pro_plus_short %}, or {% data variables.copilot.copilot_max_short %} through an in-app purchase on iOS or Android, you cannot enable additional {% data variables.product.prodname_ai_credits %}. To do so, cancel your mobile subscription and re-subscribe on {% data variables.product.prodname_dotcom_the_website %} through a web browser.
+{% data reusables.copilot.ai-credits-mobile %}
 
 ## Asking a general question about software development
 

content/copilot/tutorials/roll-out-at-scale/communicate-copilot-impact.md

@@ -0,0 +1,109 @@
+---
+title: Communicate the impact of GitHub Copilot
+shortTitle: Communicate impact
+intro: 'Support renewal, rollout, and training decisions with a clear account of {% data variables.product.prodname_copilot_short %} usage, costs, and engineering outcomes.'
+versions:
+  feature: copilot
+contentType: tutorials
+audience:
+  - driver
+allowTitleToDifferFromFilename: true
+category:
+  - Copilot usage metrics
+  - Measure success
+  - Roll Copilot out at scale
+  - Manage Copilot for a team
+---
+
+If you manage a {% data variables.product.prodname_copilot_short %} rollout, a leadership report needs to do more than show that usage is growing. It needs to explain what the evidence means for your engineering goals and recommend a decision.
+
+This tutorial helps you turn metrics and developer feedback into a short report. The example below shows how to recommend a limited expansion without claiming that {% data variables.product.prodname_copilot_short %} caused every observed improvement.
+
+## Prerequisites
+
+Gather your {% data variables.product.prodname_copilot_short %} usage data, spending records, engineering outcome measures, and developer feedback. Work with the people responsible for metrics and billing if you do not have access to those sources.
+
+For instructions on accessing usage and spending data, including the required permissions, see:
+
+* [AUTOTITLE](/copilot/how-tos/administer-copilot/view-usage-and-adoption)
+* [AUTOTITLE](/copilot/how-tos/manage-and-track-spending/manage-company-spending)
+
+Choose outcome measures that match your rollout goals before preparing the report. See [AUTOTITLE](/copilot/tutorials/roll-out-at-scale/drive-downstream-impact/achieve-company-goals).
+
+## Step 1: Define the decision
+
+Write down the decision you want the report to support and who will make it. For example, decide whether to renew licenses, expand a rollout, or invest in training.
+
+Choose evidence that answers the decision-maker's questions:
+
+* For an executive review, connect adoption to the engineering goals that matter to leadership. Summarize progress, costs, and remaining risks.
+* For a renewal, explain sustained use and observed value alongside spending. Identify adoption gaps and the plan to address them.
+* For an investment request, explain which teams or workflows to support next. State the proposed budget, expected outcomes, and how you will evaluate the investment.
+
+Use the same underlying evidence for these conversations, but lead with the findings that matter to the decision.
+
+## Step 2: Establish the comparison
+
+Make the scope of your report explicit so readers can understand what changed.
+
+1. Record the organizations, teams, and repositories included.
+1. State the reporting dates and the baseline you are comparing against. Use comparable periods and explain any differences in their length.
+1. Record the population behind each measure. For example, distinguish assigned licenses, active users, and survey respondents.
+1. Note changes in staffing, project complexity, release schedules, or engineering practices that could affect the results.
+
+If you do not have a pre-rollout baseline, say so. Use the earliest reliable period to start tracking trends, without describing it as a before-and-after comparison of adoption.
+
+Do not assume dashboard and API totals are interchangeable. Check their reporting windows and populations before combining them. See [AUTOTITLE](/copilot/reference/copilot-usage-metrics/reconciling-usage-metrics).
+
+## Step 3: Assemble the evidence
+
+Select a small set of signals that helps answer your decision question. For each finding, record its source, period, scope, and any missing data.
+
+Build your report from these types of evidence:
+
+* **Adoption:** Use active-user trends, sustained usage, and adoption cohorts to explain who is using {% data variables.product.prodname_copilot_short %} and how usage is changing.
+* **Cost:** Use spending records to describe license costs and additional usage charges. Report {% data variables.product.prodname_ai_credits_short %} consumption separately from billed spending. Include training or administration costs in your investment assessment, and label estimates.
+* **Code generation:** Use code-generation and lines-of-code trends to describe activity. Do not treat more generated code as proof of higher productivity, better quality, or shipped value.
+* **Delivery:** Compare pull request throughput and time to merge with the delivery goals you selected.
+* **Quality:** Include relevant test coverage, defects, security findings, or incidents so that faster delivery is not assessed in isolation.
+* **Developer feedback:** Summarize where developers report useful assistance, extra review work, or workflow barriers. Include the number of respondents and explain how you gathered their feedback.
+
+Use billing tools to establish spending, rather than presenting usage telemetry as an invoice total.
+
+## Step 4: Separate observations from conclusions
+
+For each finding, write what you observed before explaining what you think it means. For example, "Teams with deeper adoption merged more pull requests per user" describes an association. "{% data variables.product.prodname_copilot_short %} made those teams more productive" asserts a cause that the comparison alone does not establish.
+
+For guidance on interpreting dashboard comparisons and estimates, see [AUTOTITLE](/copilot/reference/copilot-usage-metrics/interpret-copilot-metrics).
+
+Avoid presenting usage growth or acceptance rates as a success story on their own. Explain how they relate to your chosen outcomes, and include results that did not improve.
+
+Do not convert generated lines of code or reported time savings directly into financial returns. If you include a savings estimate, document the assumptions and validate them with your finance team. Distinguish time available for other work from an actual reduction in spending.
+
+## Step 5: Write the narrative
+
+Keep the main report short, with supporting sources available for readers who need more detail.
+
+1. **State the decision and goal.** Explain what you want approved and which engineering problem it addresses.
+1. **Summarize the evidence.** Describe adoption, spending, and the outcomes most relevant to that goal.
+1. **Explain the limitations.** State what is uncertain, what else changed, and what the evidence cannot establish.
+1. **Recommend an action.** Explain why the evidence supports that action rather than a broader commitment.
+
+   * If adoption is uneven, address setup or training barriers before interpreting low usage as a lack of value.
+   * If adoption is sustained but outcome evidence is limited, continue measuring against the baseline before making a larger commitment.
+   * If outcomes and feedback support expansion, propose a staged rollout with a budget and review criteria.
+   * If costs or quality outcomes are unacceptable, recommend adjusting or pausing the affected rollout while you investigate.
+
+1. **Define the next review.** Assign an owner to the agreed action, state what success will look like, and schedule the next review. Keep the reporting scope and definitions consistent so that the next report can show whether the action helped.
+
+For example, a hypothetical rollout owner could report:
+
+> We recommend expanding the rollout to one additional team of 15 developers, with a proposed budget of $2,000 for licenses, usage, and training during October. Our goal is to reduce pull request time to merge without lowering quality.
+>
+> In September, 40 of 50 licensed developers used {% data variables.product.prodname_copilot_short %}, compared with 30 of 50 in August, our baseline month. Median pull request time to merge fell from three days to two and a half days. In a team survey, 28 of 35 respondents reported help with writing tests, but test coverage was unchanged.
+>
+> Spending remained within the rollout budget. We cannot attribute the delivery change to {% data variables.product.prodname_copilot_short %} alone because the team also changed its review process.
+>
+> The rollout owner will add test-writing training and review adoption, spending, coverage, and developer feedback at the end of October. Further expansion will depend on median time to merge staying at or below two and a half days, test coverage increasing, and spending staying within budget.
+
+Replace the example's figures and recommendation with your own evidence. If the report supports a renewal, make the renewal recommendation explicit. For an investment request, specify the resources needed rather than implying that observed trends guarantee future returns.

content/copilot/tutorials/roll-out-at-scale/index.md

@@ -10,11 +10,11 @@ children:
   - /enable-developers
   - /drive-downstream-impact
   - /measure-copilot-impact
+  - /communicate-copilot-impact
   - /measure-success
 redirect_from:
   - /copilot/rolling-out-github-copilot-at-scale
   - /copilot/tutorials/rolling-out-github-copilot-at-scale/planning-your-rollout
   - /copilot/tutorials/rolling-out-github-copilot-at-scale
 contentType: tutorials
 ---
-

content/copilot/tutorials/roll-out-at-scale/measure-copilot-impact.md

@@ -2,7 +2,7 @@
 title: Measure and demonstrate the impact of GitHub Copilot
 shortTitle: '{% data variables.product.prodname_copilot_short %} usage metrics'
 allowTitleToDifferFromFilename: true
-intro: 'Understanding how {% data variables.product.prodname_copilot_short %} is used across your enterprise is the first step to demonstrating its value. Follow this path to establish a usage baseline, see how code is being generated, and connect adoption to measurable outcomes.'
+intro: 'Use {% data variables.product.prodname_copilot_short %} metrics and engineering outcomes to assess your rollout and guide investment decisions.'
 layout: journey-landing
 versions:
   feature: copilot
@@ -42,4 +42,9 @@ journeyTracks:
     guides:
       - href: '/copilot/tutorials/roll-out-at-scale/drive-downstream-impact/achieve-company-goals'
       - href: '/copilot/how-tos/administer-copilot/view-impact-dashboard'
+  - id: 'communicate-impact'
+    title: 'Phase 5: Communicate impact and guide investment decisions'
+    description: 'Turn your findings into a clear recommendation for leadership about your next {% data variables.product.prodname_copilot_short %} investment.'
+    guides:
+      - href: '/copilot/tutorials/roll-out-at-scale/communicate-copilot-impact'
 ---

content/desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github-in-github-desktop.md

@@ -19,6 +19,8 @@ category:
 
 To keep your account secure, you must authenticate before you can use {% data variables.product.prodname_desktop %} to access resources on {% data variables.product.github %}.
 
+{% data variables.product.prodname_desktop %} uses short-lived tokens when you authenticate to {% data variables.product.prodname_dotcom_the_website %}. This improves security by limiting how long a compromised token can be used.
+
 Before you authenticate, {% data reusables.desktop.get-an-account %}
 
 {% mac %}

content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md

@@ -45,6 +45,8 @@ Organization members must also have an active SAML session to authorize an {% da
 
 {% data reusables.saml.saml-supported-idps %}
 
+{% data reusables.enterprise-accounts.gov-cloud-idp-not-supported %}
+
 Some IdPs support provisioning access to a {% data variables.product.prodname_dotcom %} organization via SCIM. For more information, see [AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations).
 
 {% data reusables.scim.enterprise-account-scim %}

content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md

@@ -32,6 +32,8 @@ These identity providers (IdPs) are compatible with the {% data variables.produc
 * Okta
 * OneLogin
 
+{% data reusables.enterprise-accounts.gov-cloud-idp-not-supported %}
+
 ## About SCIM configuration for organizations
 
 {% data reusables.scim.dedicated-configuration-account %}