diff --git a/assets/images/help/copilot/copilot-cli-context-usage.png b/assets/images/help/copilot/copilot-cli-context-usage.png deleted file mode 100644 index 1541ee8184df..000000000000 Binary files a/assets/images/help/copilot/copilot-cli-context-usage.png and /dev/null differ diff --git a/content/account-and-profile/how-tos/account-management/creating-an-account-on-github.md b/content/account-and-profile/how-tos/account-management/creating-an-account-on-github.md index 11d4483b7f43..d19200be23cd 100644 --- a/content/account-and-profile/how-tos/account-management/creating-an-account-on-github.md +++ b/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). diff --git a/content/actions/how-tos/manage-runners/use-actions-runner-controller/deploy-runner-scale-sets.md b/content/actions/how-tos/manage-runners/use-actions-runner-controller/deploy-runner-scale-sets.md index fefc06add1d2..cb1b018ecbba 100644 --- a/content/actions/how-tos/manage-runners/use-actions-runner-controller/deploy-runner-scale-sets.md +++ b/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. diff --git a/content/admin/monitoring-and-managing-your-instance/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md b/content/admin/monitoring-and-managing-your-instance/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md index ac5f58d42735..ed8c5383aad5 100644 --- a/content/admin/monitoring-and-managing-your-instance/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md +++ b/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. diff --git a/content/authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md b/content/authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md index 45a98844a6ad..385b4e80bf3e 100644 --- a/content/authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md +++ b/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
  • Brunei
  • Bulgaria
  • Burundi
    • -
  • Cambodia
  • Canada
  • Cape Verde
  • Cayman Islands
    • @@ -57,7 +56,6 @@ If your country or region is not on this list, then we aren't currently able to
  • Gambia
  • Georgia
  • Germany
    • -
  • Ghana
  • Gibraltar
  • Greece
  • Guatemala
    • diff --git a/content/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/managing-your-github-advanced-security-license-usage.md b/content/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/managing-your-github-advanced-security-license-usage.md index 780d8cb1985b..df098fd7b27b 100644 --- a/content/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/managing-your-github-advanced-security-license-usage.md +++ b/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). diff --git a/content/copilot/concepts/billing-and-usage/copilot-usage-metrics/index.md b/content/copilot/concepts/billing-and-usage/copilot-usage-metrics/index.md index cf23b13eb53a..835c87a87932 100644 --- a/content/copilot/concepts/billing-and-usage/copilot-usage-metrics/index.md +++ b/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: diff --git a/content/copilot/how-tos/copilot-on-github/chat-with-copilot/chat-in-mobile.md b/content/copilot/how-tos/copilot-on-github/chat-with-copilot/chat-in-mobile.md index 48f05a93d72e..a6f39585b292 100644 --- a/content/copilot/how-tos/copilot-on-github/chat-with-copilot/chat-in-mobile.md +++ b/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 diff --git a/content/copilot/tutorials/roll-out-at-scale/communicate-copilot-impact.md b/content/copilot/tutorials/roll-out-at-scale/communicate-copilot-impact.md new file mode 100644 index 000000000000..3a286549131d --- /dev/null +++ b/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. diff --git a/content/copilot/tutorials/roll-out-at-scale/index.md b/content/copilot/tutorials/roll-out-at-scale/index.md index 1fc77ccd6b45..63ea54fd1220 100644 --- a/content/copilot/tutorials/roll-out-at-scale/index.md +++ b/content/copilot/tutorials/roll-out-at-scale/index.md @@ -10,6 +10,7 @@ children: - /enable-developers - /drive-downstream-impact - /measure-copilot-impact + - /communicate-copilot-impact - /measure-success redirect_from: - /copilot/rolling-out-github-copilot-at-scale @@ -17,4 +18,3 @@ redirect_from: - /copilot/tutorials/rolling-out-github-copilot-at-scale contentType: tutorials --- - diff --git a/content/copilot/tutorials/roll-out-at-scale/measure-copilot-impact.md b/content/copilot/tutorials/roll-out-at-scale/measure-copilot-impact.md index 4e426c9d6284..75b5ff4d79be 100644 --- a/content/copilot/tutorials/roll-out-at-scale/measure-copilot-impact.md +++ b/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' --- diff --git a/content/desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github-in-github-desktop.md b/content/desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github-in-github-desktop.md index 8aee9e978b0c..08ee4293f169 100644 --- a/content/desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github-in-github-desktop.md +++ b/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 %} diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index 8e5aaf29f589..70a993e1fbc1 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/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 %} diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md index ef3835e40499..97d316e1643f 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md +++ b/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 %} diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md index f5d1b9525eb3..d840e6ad0f81 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md +++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md @@ -17,6 +17,8 @@ When you enable SAML SSO for your {% data variables.product.github %} organizati {% data reusables.saml.ghec-only %} +## Supported identity providers + You can find the SAML and SCIM implementation details for your IdP in the IdP's documentation. * Microsoft Active Directory Federation Services (AD FS) [SAML](https://docs.microsoft.com/windows-server/identity/active-directory-federation-services) * Microsoft Entra ID (previously known as Azure AD) [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) and [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial) @@ -25,10 +27,11 @@ You can find the SAML and SCIM implementation details for your IdP in the IdP's * PingOne [SAML](https://support.pingidentity.com/s/marketplace-integration/a7i1W0000004ID3QAM/github-connector) * Shibboleth [SAML](https://shibboleth.atlassian.net/wiki/spaces/IDP4/overview) -> [!NOTE] -> {% data variables.product.github %}'s supported identity providers for SCIM are Entra ID, Okta, and OneLogin. For more information about SCIM, see [AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations). -> -> {% data reusables.scim.enterprise-account-scim %} +{% data reusables.enterprise-accounts.gov-cloud-idp-not-supported %} + +{% data variables.product.github %}'s supported identity providers for SCIM are Entra ID, Okta, and OneLogin. For more information about SCIM, see [AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations). + +{% data reusables.scim.enterprise-account-scim %} ## SAML metadata diff --git a/content/support/learning-about-github-support/about-ticket-priority.md b/content/support/learning-about-github-support/about-ticket-priority.md index 2c29d70d929a..d5e2aa7a9c47 100644 --- a/content/support/learning-about-github-support/about-ticket-priority.md +++ b/content/support/learning-about-github-support/about-ticket-priority.md @@ -77,14 +77,16 @@ For more information about what {% data variables.contact.github_support %} can ## Ticket priorities for {% data variables.product.prodname_copilot %} -{% data variables.product.prodname_copilot_short %} is a developer productivity tool that accelerates workflows but does not gate core platform operations. If {% data variables.product.prodname_copilot_short %} is unavailable, developers can continue to write, commit, review, and deploy code using the underlying {% data variables.product.github %} platform. Platform-level outages that affect {% data variables.product.prodname_copilot_short %} availability across all users are handled through {% data variables.product.company_short %}'s incident process and reflected on [githubstatus.com](https://www.githubstatus.com). +Tickets about {% data variables.product.prodname_copilot_short %} are prioritized according to the scope and impact of the issue, as described below. Critical platform errors or outages and widespread authentication failures follow the same criteria as other {% data variables.product.prodname_ghe_cloud %} issues. Platform-level outages are handled through {% data variables.product.company_short %}'s incident process and reflected on [githubstatus.com](https://www.githubstatus.com). | Priority | Description | Examples | -| --- | --- | --- | -| {% data variables.product.support_ticket_priority_normal %} | Issues with {% data variables.product.prodname_copilot_short %} features that affect usage or productivity for members of your organization or enterprise. | | -| {% data variables.product.support_ticket_priority_low %} | Questions, suggestions, or minor issues related to {% data variables.product.prodname_copilot_short %} that are not time-sensitive. | | +| :---: | --- | --- | +| {% data variables.product.support_ticket_priority_urgent %}

    ([{% data variables.contact.premium_support %}](/support/learning-about-github-support/about-github-premium-support) only) | Critical {% data variables.product.company_short %} service errors or outages prevent your organization or enterprise from using {% data variables.product.prodname_copilot_short %}. Production workflows are critically disrupted, and no usable workaround is available. This excludes disruptions caused by network configuration, third-party software such as proxy servers, or configuration changes made by your teams. | | +| {% data variables.product.support_ticket_priority_high %} | Persistent issues prevent a team or multiple members of your organization or enterprise from using {% data variables.product.prodname_copilot_short %}, with no usable workaround. The disruption is limited to part of your organization or enterprise, or its impact on production workflows is limited. Without {% data variables.contact.premium_support %}, issues that otherwise meet the {% data variables.product.support_ticket_priority_urgent %} criteria are assigned {% data variables.product.support_ticket_priority_high %} priority. | | +| {% data variables.product.support_ticket_priority_normal %} | Issues affect your use of {% data variables.product.prodname_copilot_short %}, but affected users can continue using the service or have a usable workaround. Access issues limited to an individual user and general configuration questions also fall into this priority. | | +| {% data variables.product.support_ticket_priority_low %} | Questions that are not time-sensitive, suggestions, or minor issues that do not block productivity. | | -{% ifversion ghec %}For troubleshooting steps before contacting {% data variables.contact.github_support %}, see [AUTOTITLE](/copilot/how-tos/troubleshoot-copilot/troubleshoot-common-issues). Many {% data variables.product.prodname_copilot_short %} issues are caused by network configuration, firewalls, or proxy settings in your environment. For guidance on resolving these, see [AUTOTITLE](/copilot/how-tos/troubleshoot-copilot/troubleshoot-firewall-settings) and [AUTOTITLE](/copilot/how-tos/troubleshoot-copilot/troubleshoot-network-errors). To provide feedback on preview features, use {% data variables.contact.community_support_forum %}.{% endif %} +{% ifversion ghec %}For troubleshooting steps before contacting {% data variables.contact.github_support %}, see [AUTOTITLE](/copilot/how-tos/troubleshoot-copilot/troubleshoot-common-issues). Many {% data variables.product.prodname_copilot_short %} issues are caused by network configuration, firewalls, or proxy settings in your environment. For guidance on resolving these, see [AUTOTITLE](/copilot/how-tos/troubleshoot-copilot/troubleshoot-firewall-settings) and [AUTOTITLE](/copilot/how-tos/troubleshoot-copilot/troubleshoot-network-errors). To provide feedback on preview features, use {% data variables.contact.community_support_forum %}.{% endif %} ## Further reading diff --git a/data/features/secret-scanning-actions-logs.yml b/data/features/secret-scanning-actions-logs.yml deleted file mode 100644 index 3567c7dfcd47..000000000000 --- a/data/features/secret-scanning-actions-logs.yml +++ /dev/null @@ -1,4 +0,0 @@ -# Reference: docs-content#23361 -# Secret scanning detection for GitHub Actions workflow logs -versions: - ghec: '*' diff --git a/data/features/sub-issues.yml b/data/features/sub-issues.yml deleted file mode 100644 index 38e21ad6c9de..000000000000 --- a/data/features/sub-issues.yml +++ /dev/null @@ -1,5 +0,0 @@ -# Issue 15008 -versions: - fpt: '*' - ghec: '*' - ghes: '>=3.18' diff --git a/data/release-notes/enterprise-server/3-20/0.yml b/data/release-notes/enterprise-server/3-20/0.yml index e182de08cced..bcc568cb5943 100644 --- a/data/release-notes/enterprise-server/3-20/0.yml +++ b/data/release-notes/enterprise-server/3-20/0.yml @@ -164,6 +164,8 @@ sections: To support {% data variables.product.prodname_ghe_server %} compatibility, we're reserving the `/repos` path for a forthcoming product feature. If you currently use `/repos` for a route (for example, a User name, Organization name, a GitHub App, OAuth app, reverse proxy, or internal integration), you may need to update your configuration to avoid routing conflicts. This change ensures consistent behavior for GHES 3.20 customers and helps prevent unexpected request handling for endpoints under `/repos`. known_issues: + - | + After a user account is unsuspended, the user may remain missing from the enterprise member list and the results of GraphQL queries using `enterprise.members`. [Updated: 2026-10-30] # INCLUDE NOTES FOR RELEASE FROM "GHES Release Note Tracking" PROJECT'S "Known Issues" TAB - | Custom firewall rules are removed during the upgrade process. diff --git a/data/release-notes/enterprise-server/3-20/1.yml b/data/release-notes/enterprise-server/3-20/1.yml index 120a1b8a1c2c..063b93cb95a9 100644 --- a/data/release-notes/enterprise-server/3-20/1.yml +++ b/data/release-notes/enterprise-server/3-20/1.yml @@ -83,6 +83,8 @@ sections: - | To improve page load performance, user profile pages display a maximum of 24 organizations. When viewing your own profile, a "View all" link provides access to the full list in organization settings. When viewing another users profile, a count displays any additional organizations beyond the first 24. known_issues: + - | + After a user account is unsuspended, the user may remain missing from the enterprise member list and the results of GraphQL queries using `enterprise.members`. [Updated: 2026-10-30] - | On instances configured for high availability, you will not be able to change GitHub Actions settings through the Management Console. Other settings are not affected. [Updated: 2026-04-22] - | diff --git a/data/release-notes/enterprise-server/3-20/2.yml b/data/release-notes/enterprise-server/3-20/2.yml index 55507088d071..acb18c4765ef 100644 --- a/data/release-notes/enterprise-server/3-20/2.yml +++ b/data/release-notes/enterprise-server/3-20/2.yml @@ -57,6 +57,8 @@ sections: - | To prevent collectd memory exhaustion and OOM kills caused by write queue growth, administrators can configure collectd write queue limits and memory caps via `ghe-config`. Previously, tuning these settings required manual edits to collectd.conf and systemd configuration files. Changes take effect after running a configuration apply. known_issues: + - | + After a user account is unsuspended, the user may remain missing from the enterprise member list and the results of GraphQL queries using `enterprise.members`. [Updated: 2026-10-30] - | During an upgrade of GitHub Enterprise Server, custom firewall rules are removed. If you use custom firewall rules, you must reapply them after upgrading. - | diff --git a/data/release-notes/enterprise-server/3-20/3.yml b/data/release-notes/enterprise-server/3-20/3.yml index ee0807d4696f..d77ffd7b1da9 100644 --- a/data/release-notes/enterprise-server/3-20/3.yml +++ b/data/release-notes/enterprise-server/3-20/3.yml @@ -32,6 +32,8 @@ sections: - | The `code_scanning_alert` webhook event includes a new `assignment` action type that fires when an alert is assigned or reassigned to a user. known_issues: + - | + After a user account is unsuspended, the user may remain missing from the enterprise member list and the results of GraphQL queries using `enterprise.members`. [Updated: 2026-10-30] - | During an upgrade of GitHub Enterprise Server, custom firewall rules are removed. If you use custom firewall rules, you must reapply them after upgrading. - | diff --git a/data/release-notes/enterprise-server/3-20/4.yml b/data/release-notes/enterprise-server/3-20/4.yml index 3aae93b4b5e4..cbb8813894bc 100644 --- a/data/release-notes/enterprise-server/3-20/4.yml +++ b/data/release-notes/enterprise-server/3-20/4.yml @@ -52,6 +52,8 @@ sections: - | Site administrators can restore Enterprise Live Migrations (ELM) Exporter appliance data using GitHub Enterprise Server Backup Service. For more information, see [AUTOTITLE](/admin/backing-up-and-restoring-your-instance). known_issues: + - | + After a user account is unsuspended, the user may remain missing from the enterprise member list and the results of GraphQL queries using `enterprise.members`. [Updated: 2026-10-30] - | During an upgrade of GitHub Enterprise Server, custom firewall rules are removed. If you use custom firewall rules, you must reapply them after upgrading. - | diff --git a/data/release-notes/enterprise-server/3-20/5.yml b/data/release-notes/enterprise-server/3-20/5.yml index 7c9263457841..513eecf0e1b2 100644 --- a/data/release-notes/enterprise-server/3-20/5.yml +++ b/data/release-notes/enterprise-server/3-20/5.yml @@ -69,6 +69,8 @@ sections: - | To reduce failed repairs of large repositories or networks, such as monorepos, the timeout for repository and network repair operations has been increased. known_issues: + - | + After a user account is unsuspended, the user may remain missing from the enterprise member list and the results of GraphQL queries using `enterprise.members`. [Updated: 2026-10-30] - | During an upgrade of GitHub Enterprise Server, custom firewall rules are removed. If you use custom firewall rules, you must reapply them after upgrading. - | diff --git a/data/release-notes/enterprise-server/3-20/6.yml b/data/release-notes/enterprise-server/3-20/6.yml index e25337a67680..bb69e46d965c 100644 --- a/data/release-notes/enterprise-server/3-20/6.yml +++ b/data/release-notes/enterprise-server/3-20/6.yml @@ -61,6 +61,8 @@ sections: - | Users can see the progress of a repository being migrated with Enterprise Live Migrations (ELM). A banner indicates when the migration is in progress and the repository is still editable, when the repository has entered read-only cutover, and when the migration is complete, with a link to the destination repository. known_issues: + - | + After a user account is unsuspended, the user may remain missing from the enterprise member list and the results of GraphQL queries using `enterprise.members`. [Updated: 2026-10-30] # https://github.com/github/ghes/issues/19970 - | On appliances with 84 GB or more of RAM, MySQL could consume most available memory after an upgrade because the default InnoDB buffer pool scales with available RAM. Before adding RAM to increase memory headroom, contact GitHub Support about setting an appropriate `mysql.max-memory` limit. [Updated: 2026-09-24] diff --git a/data/release-notes/enterprise-server/3-20/7.yml b/data/release-notes/enterprise-server/3-20/7.yml index 5062aa9455f0..bdcd68ceb8ee 100644 --- a/data/release-notes/enterprise-server/3-20/7.yml +++ b/data/release-notes/enterprise-server/3-20/7.yml @@ -52,6 +52,8 @@ sections: - | Administrators can configure multiple WireGuard tunnels for high-availability deployments by setting `wireguard.num-tunnels`. Multiple tunnels distribute inter-node traffic across network queues and CPU cores, improving performance during high-volume traffic. The default configuration remains unchanged. See [Mitigating single-core softirq saturation](/admin/monitoring-and-managing-your-instance/additional-nodes/configuring-additional-nodes#mitigating-single-core-softirq-saturation). known_issues: + - | + After a user account is unsuspended, the user may remain missing from the enterprise member list and the results of GraphQL queries using `enterprise.members`. [Updated: 2026-10-30] # https://github.com/github/ghes/issues/19970 - | On appliances with 84 GB or more of RAM, MySQL could consume most available memory after an upgrade because the default InnoDB buffer pool scales with available RAM. Before adding RAM to increase memory headroom, contact GitHub Support about setting an appropriate `mysql.max-memory` limit. [Updated: 2026-09-24] diff --git a/data/release-notes/enterprise-server/3-20/8.yml b/data/release-notes/enterprise-server/3-20/8.yml index 53061b29431d..2c50abb16478 100644 --- a/data/release-notes/enterprise-server/3-20/8.yml +++ b/data/release-notes/enterprise-server/3-20/8.yml @@ -46,7 +46,7 @@ sections: - | The first user created via SAML-JIT during first-run bootstrap on a fresh GHES appliance was not added as an Enterprise owner. - | - Enterprise Managed Users could remain absent from enterprise membership listings and the `enterprise.members` GraphQL response after being reinstated. + After a user account was unsuspended, the user could remain missing from the enterprise member list and the results of GraphQL queries using `enterprise.members`. [Updated: 2026-10-30] - | On the secret scanning metrics page for a large enough enterprise, the page could time out. - | diff --git a/data/release-notes/enterprise-server/3-21/0.yml b/data/release-notes/enterprise-server/3-21/0.yml index ed4b41b45cb9..3d3a1946a7f2 100644 --- a/data/release-notes/enterprise-server/3-21/0.yml +++ b/data/release-notes/enterprise-server/3-21/0.yml @@ -235,6 +235,8 @@ sections: Starting in {% data variables.product.prodname_ghe_server %} version 3.20, we have reserved the `/repos` path for a forthcoming product feature. If you currently use `/repos` for a route (for example, a username, organization name, a GitHub App, an OAuth app, reverse proxy, or internal integration), you may need to update your configuration to avoid routing conflicts. known_issues: + - | + After a user account is unsuspended, the user may remain missing from the enterprise member list and the results of GraphQL queries using `enterprise.members`. [Updated: 2026-10-30] # Known issues from "GHES Release Note Tracking" project - | During an upgrade of GitHub Enterprise Server, custom firewall rules are removed. If you use custom firewall rules, you must reapply them after upgrading. diff --git a/data/release-notes/enterprise-server/3-21/1.yml b/data/release-notes/enterprise-server/3-21/1.yml index a4a6a161f744..7d1f7bcb0174 100644 --- a/data/release-notes/enterprise-server/3-21/1.yml +++ b/data/release-notes/enterprise-server/3-21/1.yml @@ -4,6 +4,8 @@ sections: - | **CRITICAL:** An attacker could exploit a pre-authentication server-side request forgery (SSRF) vulnerability in an upload endpoint to send crafted requests to internal services by exploiting insufficient input validation, potentially accessing internal services and exposing sensitive credentials. This attack required network access to the GHES instance. The vulnerability was addressed by adding input validation to request parameters. GitHub has requested CVE ID [CVE-2026-9312](https://www.cve.org/cverecord?id=CVE-2026-9312) for this vulnerability, which was reported via the [GitHub Bug Bounty](https://bounty.github.com/) program. known_issues: + - | + After a user account is unsuspended, the user may remain missing from the enterprise member list and the results of GraphQL queries using `enterprise.members`. [Updated: 2026-10-30] - | During an upgrade of GitHub Enterprise Server, custom firewall rules are removed. If you use custom firewall rules, you must reapply them after upgrading. - | diff --git a/data/release-notes/enterprise-server/3-21/2.yml b/data/release-notes/enterprise-server/3-21/2.yml index 9891f133b8a5..8d980572a1c5 100644 --- a/data/release-notes/enterprise-server/3-21/2.yml +++ b/data/release-notes/enterprise-server/3-21/2.yml @@ -51,6 +51,8 @@ sections: - | Site administrators can restore Enterprise Live Migrations (ELM) Exporter appliance data using GitHub Enterprise Server Backup Service. For more information, see [AUTOTITLE](/admin/backing-up-and-restoring-your-instance). known_issues: + - | + After a user account is unsuspended, the user may remain missing from the enterprise member list and the results of GraphQL queries using `enterprise.members`. [Updated: 2026-10-30] - | During an upgrade of GitHub Enterprise Server, custom firewall rules are removed. If you use custom firewall rules, you must reapply them after upgrading. - | diff --git a/data/release-notes/enterprise-server/3-21/3.yml b/data/release-notes/enterprise-server/3-21/3.yml index e07b6e9afadc..0c5fa7c46ac3 100644 --- a/data/release-notes/enterprise-server/3-21/3.yml +++ b/data/release-notes/enterprise-server/3-21/3.yml @@ -65,6 +65,8 @@ sections: To configure the limit, update `max-rsync-repairs-per-target-host` in `/data/user/common/github.conf`, then run `ghe-config-apply`. known_issues: + - | + After a user account is unsuspended, the user may remain missing from the enterprise member list and the results of GraphQL queries using `enterprise.members`. [Updated: 2026-10-30] - | During an upgrade of GitHub Enterprise Server, custom firewall rules are removed. If you use custom firewall rules, you must reapply them after upgrading. - | diff --git a/data/release-notes/enterprise-server/3-21/4.yml b/data/release-notes/enterprise-server/3-21/4.yml index 8a4e00aed479..bd695b015071 100644 --- a/data/release-notes/enterprise-server/3-21/4.yml +++ b/data/release-notes/enterprise-server/3-21/4.yml @@ -60,6 +60,8 @@ sections: - | Users can see the progress of a repository being migrated with Enterprise Live Migrations (ELM). A banner indicates when the migration is in progress and the repository is still editable, when the repository has entered read-only cutover, and when the migration is complete, with a link to the destination repository. known_issues: + - | + After a user account is unsuspended, the user may remain missing from the enterprise member list and the results of GraphQL queries using `enterprise.members`. [Updated: 2026-10-30] # https://github.com/github/ghes/issues/19970 - | On appliances with 84 GB or more of RAM, MySQL could consume most available memory after an upgrade because the default InnoDB buffer pool scales with available RAM. Before adding RAM to increase memory headroom, contact GitHub Support about setting an appropriate `mysql.max-memory` limit. [Updated: 2026-09-24] diff --git a/data/release-notes/enterprise-server/3-21/5.yml b/data/release-notes/enterprise-server/3-21/5.yml index 769219d4d26b..b06eb725113d 100644 --- a/data/release-notes/enterprise-server/3-21/5.yml +++ b/data/release-notes/enterprise-server/3-21/5.yml @@ -52,6 +52,8 @@ sections: - | Administrators can configure multiple WireGuard tunnels for high-availability deployments by setting `wireguard.num-tunnels`. Multiple tunnels distribute inter-node traffic across network queues and CPU cores, improving performance during high-volume traffic. The default configuration remains unchanged. See [Mitigating single-core softirq saturation](/admin/monitoring-and-managing-your-instance/additional-nodes/configuring-additional-nodes#mitigating-single-core-softirq-saturation). known_issues: + - | + After a user account is unsuspended, the user may remain missing from the enterprise member list and the results of GraphQL queries using `enterprise.members`. [Updated: 2026-10-30] # https://github.com/github/ghes/issues/19970 - | On appliances with 84 GB or more of RAM, MySQL could consume most available memory after an upgrade because the default InnoDB buffer pool scales with available RAM. Before adding RAM to increase memory headroom, contact GitHub Support about setting an appropriate `mysql.max-memory` limit. [Updated: 2026-09-24] diff --git a/data/release-notes/enterprise-server/3-21/6.yml b/data/release-notes/enterprise-server/3-21/6.yml index 6df7abc44d71..7e988bc19621 100644 --- a/data/release-notes/enterprise-server/3-21/6.yml +++ b/data/release-notes/enterprise-server/3-21/6.yml @@ -50,7 +50,7 @@ sections: - | The first user created via SAML-JIT during first-run bootstrap on a fresh GHES appliance was not added as an Enterprise owner. - | - Enterprise Managed Users could remain absent from enterprise membership listings and the `enterprise.members` GraphQL response after being reinstated. + After a user account was unsuspended, the user could remain missing from the enterprise member list and the results of GraphQL queries using `enterprise.members`. [Updated: 2026-10-30] - | On the secret scanning metrics page for a large enough enterprise, the page could time out. - | diff --git a/data/release-notes/enterprise-server/3-22/0.yml b/data/release-notes/enterprise-server/3-22/0.yml index d98ef264eddb..0945b940f398 100644 --- a/data/release-notes/enterprise-server/3-22/0.yml +++ b/data/release-notes/enterprise-server/3-22/0.yml @@ -193,6 +193,8 @@ sections: {% data variables.product.prodname_ghe_server %} now uses fewer CPU resources when serving REST and GraphQL API requests by skipping unused MySQL query backtrace collection. known_issues: + - | + After a user account is unsuspended, the user may remain missing from the enterprise member list and the results of GraphQL queries using `enterprise.members`. [Updated: 2026-10-30] # Known issues from "GHES Release Note Tracking" project # https://github.com/github/ghes/issues/19970 - | diff --git a/data/release-notes/enterprise-server/3-22/1.yml b/data/release-notes/enterprise-server/3-22/1.yml index a11e882a6454..1ddee99b1ad5 100644 --- a/data/release-notes/enterprise-server/3-22/1.yml +++ b/data/release-notes/enterprise-server/3-22/1.yml @@ -44,7 +44,7 @@ sections: - | The first user created via SAML-JIT during first-run bootstrap on a fresh GHES appliance was not added as an Enterprise owner. - | - Enterprise Managed Users could remain absent from enterprise membership listings and the `enterprise.members` GraphQL response after being reinstated. + After a user account was unsuspended, the user could remain missing from the enterprise member list and the results of GraphQL queries using `enterprise.members`. [Updated: 2026-10-30] - | On the secret scanning metrics page for a large enough enterprise, the page could time out. - | diff --git a/data/reusables/copilot/ai-credits-mobile.md b/data/reusables/copilot/ai-credits-mobile.md index 6664b137bf27..d4346f928eeb 100644 --- a/data/reusables/copilot/ai-credits-mobile.md +++ b/data/reusables/copilot/ai-credits-mobile.md @@ -1 +1,5 @@ -> [!NOTE] The option to purchase additional {% data variables.product.prodname_ai_credits_short %} is not available if you subscribe, or have subscribed, to a {% data variables.product.prodname_copilot_short %} plan through {% data variables.product.prodname_mobile %} on iOS or Android. +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 can't buy additional {% data variables.product.prodname_ai_credits %} through the app store. However, if your {% data variables.product.github %} account has a payment method on file, additional paid usage beyond your included {% data variables.product.prodname_ai_credits_short %} is billed to that payment method based on your budget settings. + +To avoid charges beyond your plan, create or edit a **Bundled {% data variables.product.prodname_ai_credits_short %} budget**, set it to $0 USD, and enable **Stop usage when budget limit is reached**. See [AUTOTITLE](/billing/how-tos/set-up-budgets#managing-budgets-for-your-personal-account). + +To manage all {% data variables.product.prodname_copilot_short %} billing in one place, cancel your mobile subscription in the App Store or Google Play and re-subscribe on {% data variables.product.prodname_dotcom_the_website %}. diff --git a/data/reusables/copilot/copilot-cli/cli-rewind-warning.md b/data/reusables/copilot/copilot-cli/cli-rewind-warning.md deleted file mode 100644 index 0218b807e97d..000000000000 --- a/data/reusables/copilot/copilot-cli/cli-rewind-warning.md +++ /dev/null @@ -1 +0,0 @@ -Rewinding restores your entire workspace to the state it was in at the selected snapshot. This reverts all changes made after that point—not only changes made by {% data variables.product.prodname_copilot_short %}, but also any manual edits, and changes resulting from shell commands. Any new files created in the workspace after the snapshot was taken are deleted, irrespective of their Git status. diff --git a/data/reusables/copilot/repository-custom-instructions-example.md b/data/reusables/copilot/repository-custom-instructions-example.md deleted file mode 100644 index 9795c8022d72..000000000000 --- a/data/reusables/copilot/repository-custom-instructions-example.md +++ /dev/null @@ -1,9 +0,0 @@ -This example of a `.github/copilot-instructions.md` file contains three instructions for {% data variables.product.prodname_copilot_short %}. - -```markdown -We use Bazel for managing our Java dependencies, not Maven, so when talking about Java packages, always give me instructions and code samples that use Bazel. - -We always write JavaScript with double quotes and tabs for indentation, so when your responses include JavaScript code, please follow those conventions. - -Our team uses Jira for tracking items of work. -``` diff --git a/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index 6bfda82b84ef..547b2e57b773 100644 --- a/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -29,7 +29,7 @@ To configure {% data variables.product.prodname_actions %}, you must provide ext {% endif %} -The available space on the root filesystem will be 50% of the total disk size. You can resize your instance's root disk by building a new instance or using an existing instance. For more information, see [AUTOTITLE](/admin/overview/system-overview#storage-architecture) and [AUTOTITLE](/admin/monitoring-and-managing-your-instance/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity). +The available space on the root filesystem will be 50% of the total disk size. You can resize the root disk of an existing instance. For more information, see [AUTOTITLE](/admin/overview/system-overview#storage-architecture) and [AUTOTITLE](/admin/monitoring-and-managing-your-instance/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity). ### CPU and memory diff --git a/data/reusables/gated-features/anthropic-claude.md b/data/reusables/gated-features/anthropic-claude.md deleted file mode 100644 index 4837b499686f..000000000000 --- a/data/reusables/gated-features/anthropic-claude.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_anthropic_claude %} is available in paid {% data variables.product.prodname_copilot_short %} plans. diff --git a/data/reusables/gated-features/openai-codex.md b/data/reusables/gated-features/openai-codex.md deleted file mode 100644 index 54f158f83fdf..000000000000 --- a/data/reusables/gated-features/openai-codex.md +++ /dev/null @@ -1,2 +0,0 @@ -The {% data variables.product.prodname_openai_codex %} coding agent is available for all paid [{% data variables.product.prodname_copilot_short %} plans](https://github.com/features/copilot/plans?ref_product=copilot&ref_type=purchase&ref_style=text&ref_plan=cfi). -In the {% data variables.product.prodname_openai_codex %} {% data variables.product.prodname_vscode_shortname %} extension, the **Sign in with {% data variables.product.prodname_copilot_short %}** option is available to {% data variables.copilot.copilot_pro_plus %} and {% data variables.copilot.copilot_max_short %} subscribers only. diff --git a/data/reusables/repositories/sidebar-notifications.md b/data/reusables/repositories/sidebar-notifications.md deleted file mode 100644 index 9e786d06669e..000000000000 --- a/data/reusables/repositories/sidebar-notifications.md +++ /dev/null @@ -1 +0,0 @@ -1. In the "Integrations" section of the sidebar, click **{% octicon "mail" aria-hidden="true" aria-label="mail" %} Email notifications**.