Merge pull request github#43543 from github/repo-sync

Repo sync

Author: docs-bot

assets/images/help/copilot/copilot-cli-vscode-unread-session.png

@@ -11,7 +11,6 @@ redirect_from:
   - /billing/using-the-new-billing-platform/viewing-your-subscriptions-and-billing-date
   - /billing/using-the-new-billing-platform/about-the-billing-cycle
   - /billing/managing-your-billing/about-the-billing-cycle
-product: '{% data reusables.billing.enhanced-billing-platform-product %}'
 contentType: concepts
 category:
   - Get started with billing
@@ -44,27 +43,19 @@ You can switch between annual and monthly billing from the "Licensing" page unde
 
 ## How mid-cycle changes affect your billing
 
-Mid-cycle changes to your account can affect your bill.
+Changes you make mid-cycle, such as adding or removing users, seats, or resources, can affect your bill. Some behaviors apply to both metered and volume-based billing; others are specific to one model.
 
-### Changes to metered products
+### Adding users or resources
 
-Metered products (such as {% data variables.product.prodname_actions %} minutes, {% data variables.product.prodname_registry %} storage, or {% data variables.product.prodname_codespaces %} compute) are billed based on your actual usage throughout the month. For more information on how usage is calculated for a specific product, see [Where to find usage details for specific products](#where-to-find-usage-details-for-specific-products).
-
-### Changes to volume-based products
-
-Volume-based products are billed per user, seat, or resource. Changes to these mid-cycle won’t always immediately change your bill—but they may affect your next invoice.
-
-#### Adding users or resources
-
-* **Add users or licenses**: For license-based products like {% data variables.product.prodname_copilot_short %}, {% data variables.product.prodname_enterprise %}, or {% data variables.product.prodname_GHAS %}, you'll be billed a **prorated amount** based on how many days remain in the current billing cycle.
+* **Add users or licenses**: For products like {% data variables.product.prodname_copilot_short %}, {% data variables.product.prodname_enterprise %}, or {% data variables.product.prodname_GHAS %}, you'll be billed a prorated amount for the added licenses based on how many days remain in the current billing cycle.
 * **Add organizations or repositories**: These will also result in **prorated charges**, which appear on your next invoice.
 
-#### Removing users or resources
+### Removing users or resources
 
-* **Remove users or seats**: The user’s access is revoked immediately, but you'll still be billed for the **full billing cycle**. Removing a user won't reduce your current bill.
+* **Remove users or seats**: The user's access is revoked immediately, but you'll still be billed for the **full billing cycle**. Removing a user won't reduce your current bill.
 * **Remove organizations or repositories**: Charges **stop immediately** when removed, but you'll still be billed for any usage **up to that point**.
 
-#### Transferring users or resources
+### Transferring users or resources
 
 * **Within the same billing account**: No double-billing. Moving users or resources between organizations under the same account is handled automatically.
 * **Between different billing accounts**: Each account is billed according to its own cycle. You may see charges in both accounts if the move overlaps billing periods.

content/billing/concepts/billing-cycles.md

@@ -39,7 +39,6 @@ redirect_from:
   - /billing/using-the-new-billing-platform/about-billing-for-git-large-file-storage
   - /billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage
 shortTitle: Git LFS
-product: '{% data reusables.billing.enhanced-billing-platform-product %}'
 contentType: concepts
 category:
   - Understand product costs

content/billing/concepts/product-billing/git-lfs.md

@@ -14,12 +14,12 @@ category:
   - Set up payment
 ---
 
-
 ## About the Reserve Bank of India's recurring payments regulation
 
 A new payments regulation from the Reserve Bank of India (RBI) recently came into effect. This regulation places additional requirements on recurring online transactions and has prevented some {% data variables.product.company_short %} customers in India from making recurring payments. Customers using payment methods issued in India for any recurring transactions on {% data variables.product.github %} may find that their payments are declined by their banks or card issuers. For more information, see [the RBI's press release](https://www.rbi.org.in/Scripts/BS_PressReleaseDisplay.aspx?prid=51353).
 
 The regulation applies to all recurring transactions, including:
+
 * {% data variables.product.prodname_dotcom %} plan subscriptions (Pro, Team, Enterprise)
 * {% data variables.product.prodname_marketplace %} purchases
 * {% data variables.product.prodname_sponsors %} transactions
@@ -50,7 +50,7 @@ In the meantime, we are actively working with our payment partners to restore re
 
 Existing sponsorships will remain in place during this period and maintainers will continue to be paid out as expected. Payments for the accrued sponsorship amounts from the funding account will be collected at the same time as other accrued charges.
 
-## Making a one-time payment for a GitHub subscription
+## Making a one-time payment for a {% data variables.product.github %} subscription
 
 > [!NOTE]
 > Affected customers will receive an email notification with a link to their billing settings when payment is due. Two further reminder emails will be sent 7 and 14 days later if payment has not been made. After 14 days, paid features and services will be locked until payment is made.
@@ -61,4 +61,8 @@ Existing sponsorships will remain in place during this period and maintainers wi
 1. Review your billing and payment information.
 1. Optionally, if you need to make an edit, click **Edit** next to the relevant section.
 1. Click **Submit payment**.
+
+   > [!NOTE]
+   > PayPal is not supported as a payment method for one-time payments. If your saved payment method is a PayPal account, **Submit payment** will be disabled. To complete your payment, update your payment method to a credit or debit card. You can enter card details directly on the payment page.
+
 1. Once payment for the current billing cycle has been successfully made, the **Pay now** button on your "Billing & plans" page will be disabled until your next payment is due.

content/billing/how-tos/set-up-payment/india-one-time-payments.md

@@ -42,15 +42,27 @@ When {% data variables.product.github %} detects a vulnerable dependency, a {% d
 
 For information about viewing and managing alerts, see [AUTOTITLE](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts).
 
-## Enabling alerts
+## Who can enable alerts?
 
 Repository administrators and organization owners can enable {% data variables.product.prodname_dependabot_alerts %} for their repositories{% ifversion fpt or ghec %} and organizations{% endif %}. When enabled, {% data variables.product.github %} immediately generates the dependency graph and creates alerts for any vulnerable dependencies it identifies. {% ifversion fpt or ghec %} Repository administrators can grant access to additional people or teams.{% endif %}
 
 {% data reusables.repositories.enable-security-alerts %}
 
 See [AUTOTITLE](/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts).
 
-## Notifications for alerts
+{% ifversion dependabot-alerts-assignees %}
+
+## Alert ownership and assignments
+
+Users with write access or higher can assign {% data variables.product.prodname_dependabot_alerts %} to repository collaborators, teams, or {% data variables.product.prodname_copilot_short %} to establish clear ownership for vulnerability remediation. Assignments help track who's responsible for each alert and prevent vulnerabilities from being overlooked.
+
+When an alert is assigned, the assignee receives a notification and the alert displays their name in the alert list. You can filter alerts by assignee to track progress. Assigning an alert to {% data variables.product.prodname_copilot_short %} automatically generates a fix and opens a draft pull request for review.
+
+For information about assigning alerts, see [AUTOTITLE](/code-security/how-tos/manage-security-alerts/manage-dependabot-alerts/viewing-and-updating-dependabot-alerts#viewing-and-prioritizing-dependabot-alerts).
+
+{% endif %}
+
+## How alert notifications work
 
 By default, {% data variables.product.github %} sends email notifications about new alerts to people who both:
 
@@ -82,7 +94,7 @@ Alternatively, you can opt into the weekly email digest, or even completely turn
 
 {% ifversion copilot-chat-ghas-alerts %}
 
-## Asking {% data variables.copilot.copilot_chat %} about alerts
+## {% data variables.copilot.copilot_chat %} integration
 
 With a {% data variables.copilot.copilot_enterprise %} license, you can ask {% data variables.copilot.copilot_chat_short %} questions about {% data variables.product.prodname_dependabot_alerts %} in your organization's repositories. For more information, see [AUTOTITLE](/copilot/using-github-copilot/asking-github-copilot-questions-in-githubcom#asking-questions-about-alerts-from-github-advanced-security-features).
 

content/code-security/concepts/supply-chain-security/about-dependabot-alerts.md

@@ -58,7 +58,7 @@ By default, alerts are sorted by **Most important**, which helps you prioritize
    ![Screenshot showing the "Tags" section in the alert details page.](/assets/images/help/repository/dependabot-alerts-tags-section.png)
 
 {% ifversion dependabot-alerts-assignees %}
-1. On the right panel,  select an assignee by using the **Assignees** dropdown list. This clearly communicates who is responsible for triaging the alert so that no effort is wasted on repetitive analysis without worrying that alerts might fall through the cracks.
+1. On the right panel, select an assignee by using the **Assignees** dropdown list. You can assign the alert to a user or team to establish clear ownership, or assign it to {% data variables.product.prodname_copilot_short %} to automatically generate a fix. This clearly communicates who is responsible for triaging the alert and helps you avoid repetitive analysis. It also ensures that alerts are not missed.
 {% endif %}
 
 1. Optionally, to suggest an improvement to the related security advisory, on the right-hand side of the alert details page, click **Suggest improvements for this advisory on the {% data variables.product.prodname_advisory_database %}**. See [AUTOTITLE](/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/editing-security-advisories-in-the-github-advisory-database).

content/code-security/how-tos/manage-security-alerts/manage-dependabot-alerts/viewing-and-updating-dependabot-alerts.md

@@ -189,6 +189,9 @@ For more information about production context, see [AUTOTITLE](/code-security/se
 
 | Qualifier | Description |
 | -------- | -------- |
+|{% ifversion dependabot-alerts-assignees %}|
+| `assignee` | Display alerts by assignee username or team, for example: `assignee:@octocat`, `assignee:@copilot`, or `assignee:@github/security-team`.|
+|{% endif %}|
 |`ecosystem`|Display {% data variables.product.prodname_dependabot_alerts %} detected in a specified ecosystem, for example: `ecosystem:Maven`.|
 |{% ifversion fpt or ghec or ghes > 3.15 %}|
 |`epss_percentage`|Display {% data variables.product.prodname_dependabot_alerts %} whose EPSS score meets the defined criteria, for example: `epss_percentage:>=0.01`|

content/code-security/reference/security-at-scale/available-filters-for-security-overview.md

@@ -39,9 +39,10 @@ An LTS model is an AI model that {% data variables.product.github %} commits to
 
 ## Continuous access when premium requests are unavailable
 
-{% data variables.copilot.copilot_gpt_53_codex %} is available on paid plans with a 0x premium request multiplier, which means it does not consume premium requests. This ensures continuous access to {% data variables.product.prodname_copilot_short %} in situations such as:
-* Premium request quota exhausted: If a user has used their monthly premium request allowance, they can continue working with {% data variables.copilot.copilot_gpt_41 %} (the former base model) at no additional cost.
-* Overage controls disabled: If an organization or enterprise has disabled premium request overages and a user reaches their limit, {% data variables.copilot.copilot_gpt_53_codex %} will not remain available.
+{% data variables.copilot.copilot_gpt_53_codex %} is available on paid plans with a 1x premium request multiplier, which means it consumes premium requests. To ensure continuous access to {% data variables.product.prodname_copilot_short %} when premium requests are unavailable:
+
+* Premium request quota exhausted: If a user has used their monthly premium request allowance, {% data variables.product.prodname_copilot_short %} automatically falls back to {% data variables.copilot.copilot_gpt_41 %} (the former base model) at no additional cost to the user.
+* Overage controls disabled: If an organization or enterprise has disabled premium request overages and a user reaches their limit, {% data variables.product.prodname_copilot_short %} will fall back to {% data variables.copilot.copilot_gpt_41 %}.
 
 ## Further reading