Merge pull request #33924 from github/repo-sync

Repo sync

content/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot.md

@@ -76,11 +76,7 @@ For a {% data variables.product.prodname_copilot_enterprise %} subscription, all
 For {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_ghe_cloud %}, policy settings and the usage overview are available at the enterprise level. For more information, see "[AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise)" and "[AUTOTITLE](/enterprise-cloud@latest/billing/managing-billing-for-github-copilot/viewing-your-github-copilot-usage)."
 {% endif %}
 
-{% note %}
-
-**Note:** {% data variables.product.prodname_copilot %} billing operates in Coordinated Universal Time (UTC), but it calculates your bill according to the timezone of your billing cycle. For example, if you're billed through Azure and your current billing cycle ends at 11:59 PM EST on December 1st, canceling a seat at 7:00 PM EST on December 1st might show the seat cancellation at 12:00 AM UTC on December 2nd. However, the seat would end within the billing cycle that you requested the cancellation, and you would not pay for that seat in the following cycle.
-
-{% endnote %}
+> [!NOTE] {% data variables.product.prodname_copilot %} billing operates in Coordinated Universal Time (UTC), but it calculates your bill according to the timezone of your billing cycle. For example, if you're billed through Azure and your current billing cycle ends at 11:59 PM EST on December 1st, canceling a seat at 7:00 PM EST on December 1st might show the seat cancellation at 12:00 AM UTC on December 2nd. However, the seat would end within the billing cycle that you requested the cancellation, and you would not pay for that seat in the following cycle.
 
 ### About seat assignment for {% data variables.product.prodname_copilot_for_business %} and {% data variables.product.prodname_copilot_enterprise %}
 
@@ -98,11 +94,7 @@ If you are a member of an organization or enterprise with a {% data variables.pr
 
 When you connect an Azure subscription to your organization or enterprise account and enable metered billing via Azure, metered usage will start to be sent to Azure. You will be billed through {% data variables.product.prodname_dotcom %} for usage from the start of the current billing cycle to when you enabled metered billing via Azure, on your next billing date. The period between the date you connected your Azure subscription and enabled metered billing via Azure, and the end of the calendar month will be charged in Azure on the first of the month. For more information, see "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription)."
 
-{% note %}
-
-**Note:** Usage data is sent to Azure daily, but you are billed at the end of the month based on the number of seats used. This means that although you can track your daily spending (number of seats in this case), actual payments are processed monthly.
-
-{% endnote %}
+> [!NOTE] Usage data is sent to Azure daily, but you are billed at the end of the month based on the number of seats used. This means that although you can track your daily spending (number of seats in this case), actual payments are processed monthly.
 
 ### About changes to your {% data variables.product.prodname_copilot_enterprise %} subscription
 

content/copilot/managing-copilot/configure-personal-settings/configuring-network-settings-for-github-copilot.md

@@ -36,11 +36,7 @@ If you don't configure a proxy directly in your editor, {% data variables.produc
 * `HTTP_PROXY`
 * `http_proxy`
 
-{% note %}
-
-**Note:** You can use any of these variables to store the URL of a standard HTTP proxy. In standard usage, the `http` and `https` portions of these variables refer to the type of request being made, not the URL of the proxy itself. {% data variables.product.prodname_copilot %} does not follow this convention and uses the URL stored in the variable with the highest priority as the proxy for both HTTP and HTTPS requests.
-
-{% endnote %}
+> [!NOTE] You can use any of these variables to store the URL of a standard HTTP proxy. In standard usage, the `http` and `https` portions of these variables refer to the type of request being made, not the URL of the proxy itself. {% data variables.product.prodname_copilot %} does not follow this convention and uses the URL stored in the variable with the highest priority as the proxy for both HTTP and HTTPS requests.
 
 If you have configured a proxy but are still encountering connection errors, see "[AUTOTITLE](/copilot/troubleshooting-github-copilot/troubleshooting-network-errors-for-github-copilot#troubleshooting-proxy-errors)."
 
@@ -54,11 +50,7 @@ If you have configured a proxy but are still encountering connection errors, see
 1. In the "Host name" field, enter the hostname of your proxy server, and in the "Port number" field, enter the port number of your proxy server.
 1. Optionally, to configure {% data variables.product.prodname_copilot_short %} to ignore certificate errors, in the left sidebar, click **Tools**, click **Server Certificates**, then select or deselect **Accept non-trusted certificates automatically**.
 
-   {% warning %}
-
-   **Warning:** Ignoring certificate errors can cause security issues and is not recommended.
-
-   {% endwarning %}
+   > [!WARNING] Ignoring certificate errors can cause security issues and is not recommended.
 
 ### Basic authentication
 
@@ -77,11 +69,7 @@ This stores your credentials as plaintext in your editor's settings. Alternative
 1. In the text box under "Proxy", type the address of your proxy server, for example `http://localhost:3128`.
 1. Optionally, to configure {% data variables.product.prodname_copilot_short %} to ignore certificate errors, under "Proxy Strict SSL", select or deselect the checkbox.
 
-   {% warning %}
-
-   **Warning:** Ignoring certificate errors can cause security issues and is not recommended.
-
-   {% endwarning %}
+   > [!WARNING] Ignoring certificate errors can cause security issues and is not recommended.
 
 ### Basic authentication
 
@@ -147,11 +135,7 @@ If the default SPN isn't correct for your proxy, you can override the SPN in {%
 
 Generally, if you're using company equipment, your company's IT department should have already installed any required certificates on your machine. If you need to install a certificate, see the following instructions.
 
-{% warning %}
-
-**Warning:** Installing a custom certificate is an instruction for your computer to trust the creator of the certificate, potentially allowing the creator to intercept all Internet traffic from your machine. You should be very careful to verify that you are installing the correct certificate.
-
-{% endwarning %}
+> [!WARNING] Installing a custom certificate is an instruction for your computer to trust the creator of the certificate, potentially allowing the creator to intercept all Internet traffic from your machine. You should be very careful to verify that you are installing the correct certificate.
 
 * For Windows, see [Installing the trusted root certificate](https://learn.microsoft.com/en-us/skype-sdk/sdn/articles/installing-the-trusted-root-certificate) in the Microsoft documentation.
 * For macOS, see [Add certificates to a keychain using Keychain Access on Mac](https://support.apple.com/en-gb/guide/keychain-access/kyca2431/mac) in the Keychain Access User Guide.

content/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-access-to-github-copilot-in-your-organization/granting-access-to-copilot-for-members-of-your-organization.md

@@ -38,11 +38,9 @@ Billing for {% data variables.product.prodname_copilot %} starts when you grant
 ## Granting access to {% data variables.product.prodname_copilot %} for specific users in your organization
 
 {% ifversion ghec %}
-{% note %}
 
-**Note:** You can automatically enable access for every member of a group in your identity provider (IdP) by synchronizing that group with a {% data variables.product.prodname_dotcom %} team, then giving that team access to {% data variables.product.prodname_copilot %}.  For more information, see "[AUTOTITLE](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)."
+> [!NOTE] You can automatically enable access for every member of a group in your identity provider (IdP) by synchronizing that group with a {% data variables.product.prodname_dotcom %} team, then giving that team access to {% data variables.product.prodname_copilot %}.  For more information, see "[AUTOTITLE](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)."
 
-{% endnote %}
 {% endif %}
 
 {% data reusables.profile.access_org %}
@@ -70,11 +68,7 @@ Billing for {% data variables.product.prodname_copilot %} starts when you grant
 
      To add members in bulk, click **Choose CSV to upload**, and then upload a CSV file including either the username or email address for each member you want to add, separated by a comma. The file can contain a mixture of usernames and email addresses.
 
-     {% warning %}
-
-     **Warning:** When you upload a CSV file, unless you're using {% data variables.product.prodname_emus %}, {% data variables.product.prodname_copilot %} will search all users on {% data variables.product.prodname_dotcom_the_website %} for matches. If the CSV includes users who are not members of your organization, they will be invited to join your organization when you click **Continue to purchase** followed by **Purchase seats**. This warning does not apply to accounts using {% data variables.product.prodname_emus %}.
-
-     {% endwarning %}
+     > [!WARNING] When you upload a CSV file, unless you're using {% data variables.product.prodname_emus %}, {% data variables.product.prodname_copilot %} will search all users on {% data variables.product.prodname_dotcom_the_website %} for matches. If the CSV includes users who are not members of your organization, they will be invited to join your organization when you click **Continue to purchase** followed by **Purchase seats**. This warning does not apply to accounts using {% data variables.product.prodname_emus %}.
 
      Review the list of users generated from your CSV file. Clear the selection of any users you do not want to add.
 

content/copilot/managing-copilot/managing-github-copilot-in-your-organization/reviewing-github-copilot-activity-in-your-organization/reviewing-usage-data-for-github-copilot-in-your-organization.md

@@ -38,11 +38,7 @@ You can use {% data variables.product.prodname_dotcom %}'s REST API to get detai
 
 ## Understanding the `last_activity_at` calculation
 
-{% note %}
-
-**Note:** This data is in public beta and subject to change.
-
-{% endnote %}
+> [!NOTE] This data is in public beta and subject to change.
 
 To align the `last_activity_at` data point with _actual usage_, the system returns the timestamp of a user's most recent interaction with Copilot functionality. These interactions are:
 

content/copilot/responsible-use-of-github-copilot-features/responsible-use-of-github-copilot-chat-in-githubcom.md

@@ -28,11 +28,7 @@ redirect_from:
 
 The chat interface provides access to coding information and support without requiring you to navigate documentation or search online forums.
 
-{% note %}
-
-**Note**: {% data variables.product.prodname_copilot_chat_short %} is also available in {% data variables.product.prodname_vscode %}, {% data variables.product.prodname_vs %}, and the JetBrains suite of IDEs. However, features available in these IDEs differ from features available on {% data variables.product.prodname_dotcom_the_website %}.
-
-{% endnote %}
+> [!NOTE] {% data variables.product.prodname_copilot_chat_short %} is also available in {% data variables.product.prodname_vscode %}, {% data variables.product.prodname_vs %}, and the JetBrains suite of IDEs. However, features available in these IDEs differ from features available on {% data variables.product.prodname_dotcom_the_website %}.
 
 {% data variables.product.prodname_copilot_chat %} can answer a wide range of coding-related questions on topics including syntax, programming concepts, test cases, debugging, and more. {% data variables.product.prodname_copilot_chat %} is not designed to answer non-coding questions or provide general information on topics outside of coding.
 

content/copilot/troubleshooting-github-copilot/troubleshooting-common-issues-with-github-copilot.md

@@ -37,13 +37,8 @@ When a file is affected by a content exclusion setting, {% data variables.produc
 
 {% data reusables.copilot.content-exclusions-delay %} For more information, see "[AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-github-copilot-features-in-your-organization/testing-changes-to-content-exclusions-in-your-ide#propagating-content-exclusion-changes-to-your-ide)."
 
-{% note %}
-
-**Notes:**
-
-{% data reusables.copilot.content-exclusion-limitations %}
-
-{% endnote %}
+> [!NOTE]
+> {% data reusables.copilot.content-exclusion-limitations %}
 
 ## Error: "{% data variables.product.prodname_copilot %} could not connect to server. Extension activation failed"
 

content/copilot/troubleshooting-github-copilot/troubleshooting-network-errors-for-github-copilot.md

@@ -66,11 +66,7 @@ Some possible ways to resolve certificate-related errors are:
   * On Linux, {% data variables.product.prodname_copilot_short %} checks the standard OpenSSL files `/etc/ssl/certs/ca-certificates.crt` and `/etc/ssl/certs/ca-bundle.crt`.
 * Configure {% data variables.product.prodname_copilot %} to ignore certificate errors. In your proxy settings, you can deselect **Proxy Strict SSL** in {% data variables.product.prodname_vscode %}, or select **Accept non-trusted certificates automatically** in a JetBrains IDE. For more information, see "[AUTOTITLE](/copilot/configuring-github-copilot/configuring-network-settings-for-github-copilot#configuring-proxy-settings-for-github-copilot)."
 
-  {% warning %}
-
-  **Warning:** Ignoring certificate errors can cause security issues and is not recommended.
-
-  {% endwarning %}
+  > [!WARNING] Ignoring certificate errors can cause security issues and is not recommended.
 
 ### Troubleshooting security software-related certificate errors