Merge branch 'main' into patch-1

Author: bnetsera92-stack

content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-governance.md

@@ -29,7 +29,7 @@ Rulesets allow you to flexibly target the organizations, repositories, and branc
 
 * To target **organizations**, you can select all, choose from a list, define a dynamic pattern for organization names using `fnmatch` syntax, or use organization custom properties to dynamically target organizations based on metadata. For syntax details, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository#using-fnmatch-syntax). For information on custom properties, see [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/custom-properties).
 
-* Within those organizations, you can target all **repositories**, or target a dynamic list by custom property. See [AUTOTITLE](/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization).
+* Within those organizations, you can target all **repositories**, or target a dynamic list by custom property or deployment context.
 * Within the repositories, you can target certain **branches or tags**: all branches, the default branch, or a dynamic list using `fnmatch` syntax.
 
 When you create a ruleset that targets branches in a repository, repository administrators can no longer rename branches or change the default branch in the targeted repository. They can still create and delete branches if they have the appropriate permissions.
@@ -78,7 +78,12 @@ If you set a dynamic list, you'll add one or more naming patterns using `fnmatch
 
 ### Choosing which repositories to target in your enterprise
 
-Within the selected organizations, you can target all repositories or target a dynamic list by custom property. See [AUTOTITLE](/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization).
+Within the selected organizations, you can target all repositories or target a dynamic list based on a filter:
+
+* You can filter by custom property. See [AUTOTITLE](/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization).
+{%- ifversion virtual-registry %}
+* {% data reusables.security.deployable-rulesets %}
+{%- endif %}
 
 ### Choosing which branches or tags to target
 

content/billing/concepts/product-billing/github-copilot-licenses.md

@@ -40,14 +40,6 @@ There are several ways to use {% data variables.product.prodname_copilot_short %
 * Intended for **individual use only** (not suitable for organizations or enterprises).
 * For usage beyond the free plan limits, upgrade to {% data variables.copilot.copilot_pro_short %}.
 
-### 30-day trial for {% data variables.copilot.copilot_pro_short %}
-
-* Before starting a paid plan for a personal account, you can activate a **one-time 30-day trial**. [Start using {% data variables.copilot.copilot_free_short %}](https://github.com/copilot).
-* You must provide a payment method.
-* If you do not cancel before the end of the trial, it automatically converts to a paid plan.
-* You can cancel any time during the 30 days. If you cancel, you will not be charged and will keep access until the trial ends.
-* Free trials are limited to three per payment method. Additional trials will continue as paid subscriptions.
-
 ### Educational and open source benefits
 
 * {% data variables.copilot.copilot_student_short %} offers free access to {% data variables.product.prodname_copilot_short %}'s premium features for verified students. See [AUTOTITLE](/copilot/how-tos/manage-your-account/free-access-with-copilot-student).

content/code-security/concepts/supply-chain-security/linked-artifacts.md

@@ -13,11 +13,12 @@ The {% data variables.product.virtual_registry %} provides a unified view of sof
 
 The page shows you how an artifact was built, where it is stored or running, and which compliance and security metadata is associated with the artifact.
 
-Teams in your organization can use the {% data variables.product.virtual_registry %} to:
+Teams in your organization can use data from the {% data variables.product.virtual_registry %} to:
 
 * Prioritize alerts from {% data variables.product.prodname_GHAS %} features based on whether the detected vulnerabilities are running in production or exposed to the internet
 * Quickly connect artifacts to build details, storage locations, and owning teams
 * Meet compliance by exporting auditable proof of your artifacts' provenance and integrity
+* Find repositories that are associated with a deployed artifact, and target them in branch rulesets
 
 ## Which artifacts appear on the {% data variables.product.virtual_registry %}?
 
@@ -43,12 +44,20 @@ For more information about attestations and SLSA levels, see [AUTOTITLE](/action
 
 ### Deployment records
 
-Deployment records include the environment where the artifact is deployed and any runtime risks (such as "sensitive data" or "internet exposed") associated with the artifact. You can use this data to filter security alerts based on the level of threat posed to your organization and consumers.
+Deployment records include the environment where the artifact is deployed and any runtime risks (such as "sensitive data" or "internet exposed") associated with the artifact.
 
 ![Screenshot of an artifact page. Highlighted fields: the "Deployments" list, including tags for "Prod", "sensitive data", and "pacific-east".](/assets/images/help/security/virtual-registry-deployment-record.png)
 
 >[!NOTE] Deployment records do **not** include deployment activity from a repository's deployments dashboard, which comes from a different source. See [AUTOTITLE](/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository).
 
+## Where is artifact data available?
+
+As well as being available on the {% data variables.product.virtual_registry %} itself, artifact metadata is integrated into policy and security surfaces on {% data variables.product.github %}. Teams can use this data to make policy decisions or prioritize security issues. For example, they can:
+
+* Use `deployed` or `deployable` filters to search for repositories or target repositories in organization and enterprise rulesets. See [AUTOTITLE](/search-github/searching-on-github/searching-for-repositories#search-based-on-deployment-context).
+* Filter security campaigns, {% data variables.product.prodname_code_scanning %} alerts, and {% data variables.product.prodname_dependabot %} alerts by runtime risk. See [AUTOTITLE](/code-security/tutorials/secure-your-organization/prioritize-alerts-in-production-code).
+* View runtime risks as attributes on individual {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_dependabot %} alerts.
+
 ## How does the {% data variables.product.virtual_registry %} fit into my processes?
 
 This example workflow shows how the {% data variables.product.virtual_registry %} integrates with other {% data variables.product.github %} features and external systems.

content/code-security/reference/supply-chain-security/dependabot-options-reference.md

@@ -682,8 +682,6 @@ Reviewers must have at least read access to the repository.
 | {% endif %} |
 | [`timezone`](#timezone) | Specify the timezone of the `time` value.  |
 
-{% ifversion fpt or ghec %}
-
 ### `interval`
 
 Supported values: `daily`, `weekly`, `monthly`, `quarterly`, `semiannually`, `yearly`, or `cron`
@@ -698,22 +696,12 @@ Each package manager **must** define a schedule interval.
 * Use `yearly` to run on the first day of January.
 * Use `cron` for cron expression based scheduling option. See [`cronjob`](#cronjob).
 
-{% elsif ghes %}
-
-### `interval`
-
-Supported values: `daily`, `weekly`, `monthly`{% ifversion dependabot-schedule-updates %}, or `cron`{% endif %}
-
-Each package manager **must** define a schedule interval.
+>[!NOTE]
+> The supported values `quarterly`, `semiannually`, and `yearly` are only available on {% data variables.product.prodname_ghe_server %} from version 3.19.
 
-* Use `daily` to run on every weekday, Monday to Friday.
-* Use `weekly` to run once a week, by default on Monday.
-* Use `monthly` to run on the first day of each month.{% ifversion dependabot-schedule-updates %}
-* Use `cron` for cron expression based scheduling option. See [`cronjob`](#cronjob).{% endif %}
+By default, {% data variables.product.prodname_dependabot %} randomly assigns a time to apply all the updates in the configuration file. You can use the `time` and `timezone` parameters to set a specific runtime for all intervals.  {% ifversion dependabot-schedule-updates %}If you use a `cron` interval, you can define the update time with a `cronjob` expression.{% endif %}
 
-{% endif %}
 
-By default, {% data variables.product.prodname_dependabot %} randomly assigns a time to apply all the updates in the configuration file. You can use the `time` and `timezone` parameters to set a specific runtime for all intervals.  {% ifversion dependabot-schedule-updates %}If you use a `cron` interval, you can define the update time with a `cronjob` expression.{% endif %}
 
 ### `day`
 

content/code-security/tutorials/secure-your-organization/prioritize-alerts-in-production-code.md

@@ -25,7 +25,7 @@ To provide production context, you should configure your system to:
 * Update **storage records** in the {% data variables.product.virtual_registry %} whenever an artifact is promoted to a production-approved package repository.
 * Update **deployment records** when an artifact is deployed to a production environment.
 
-{% data variables.product.github %} processes this metadata and uses it to power alert filters, such as `artifact-registry-url` and `artifact-registry` from storage records, and `has:deployment` and `runtime-risk` from deployment records.
+{% data variables.product.github %} processes this metadata and uses it to power alert filters, such as `artifact-registry-url` and `artifact-registry` from storage records, and `has:deployment` and `runtime-risk` from deployment records. Runtime risks from deployment records are also visible as properties on individual {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_dependabot %} alert pages.
 
 For more information on updating records, see [AUTOTITLE](/code-security/how-tos/secure-your-supply-chain/establish-provenance-and-integrity/upload-linked-artifacts).
 

content/copilot/concepts/billing/billing-for-individuals.md

@@ -31,15 +31,9 @@ category:
 
 {% ifversion fpt %}
 
-### About the 30-day trial for {% data variables.copilot.copilot_pro_short %}
+> [!NOTE] {% data variables.copilot.copilot_pro_short %} and {% data variables.copilot.copilot_pro_plus_short %} are paid plans. Billing starts when you subscribe. If you already have a billing cycle, charges are prorated and included in your next bill.
 
-> [!NOTE] {% data variables.copilot.copilot_pro_plus_short %} does not include a trial. You will be billed immediately upon subscribing.
-
-Before starting a paid plan for a personal account, you can set up a one-time {% data reusables.copilot.trial-period %}-day trial to evaluate {% data variables.product.prodname_copilot_short %}. To begin a trial, you will need to provide a payment method. If you do not cancel the trial before the end of the {% data reusables.copilot.trial-period %} days, the trial will automatically convert to a paid plan.
-
-You can cancel your {% data variables.product.prodname_copilot_short %} trial at any time during the {% data reusables.copilot.trial-period %} days and you won't be charged. If you cancel before the end of the trial, you will continue to have access to {% data variables.product.prodname_copilot_short %} until the {% data reusables.copilot.trial-period %}-day trial period ends. See [AUTOTITLE](/copilot/managing-copilot/managing-copilot-as-an-individual-subscriber/canceling-your-copilot-trial-as-an-individual-user).
-
-{% data reusables.copilot.tp-users-trial-eligibility %}{% endif %}
+{% endif %}
 
 ## About premium requests
 
@@ -71,7 +65,7 @@ You can cancel your {% data variables.product.prodname_copilot_short %} plan at
 Your billing date will depend on whether or not you are already being billed by {% data variables.product.prodname_dotcom %}.
 
 * **If you are not already being billed by {% data variables.product.prodname_dotcom %}**, in most cases your billing cycle will start on the day you sign up for {% data variables.product.prodname_copilot_short %}. For example, if you sign up on 3 September, with monthly billing, your initial billing cycle will run from 3 September until and including 2 October, and then on the same days of subsequent months.
-* **If you already have a billing cycle**, billing for {% data variables.product.prodname_copilot_short %} will be included in your next bill, or your first bill after the end of your 30-day {% data variables.product.prodname_copilot_short %} trial. You will be charged on a pro rata basis for that initial period. If you do not already have an established billing date, you will be billed for {% data variables.copilot.copilot_pro_short %} at the end of your 30-day trial, or when you set up a new paid {% data variables.product.prodname_copilot_short %} plan.
+* **If you already have a billing cycle**, billing for {% data variables.product.prodname_copilot_short %} will be included in your next bill. You will be charged on a pro rata basis for that initial period.
 
 ## Further reading
 

content/copilot/get-started/choose-enterprise-plan.md

@@ -65,15 +65,9 @@ For more information on managing spending on premium requests, see [AUTOTITLE](/
 
 ## Getting started
 
-When you've determined whether premium requests and {% data variables.copilot.copilot_enterprise_short %} features will help you achieve your goals, it's time to choose a plan.
+When you've determined whether premium requests and {% data variables.copilot.copilot_enterprise_short %} features will help you achieve your goals, it's time to choose a plan. Contact our Sales team to get started with {% data variables.copilot.copilot_business_short %} or {% data variables.copilot.copilot_enterprise_short %}.
 
-{% note %}
-
-Sign up:
-
-<a href="https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button&ref_plan=business" target="_blank" class="btn btn-outline mt-3 mr-3 no-underline"><span>Copilot Business</span></a>  <a href="https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button&ref_plan=enterprise" target="_blank" class="btn btn-outline mt-3 mr-3 no-underline"><span>Copilot Enterprise</span></a>
-
-{% endnote %}
+<a href="https://github.com/enterprise/contact?ref_product=copilot&ref_type=engagement&ref_style=button" target="_blank" class="btn btn-outline mt-3 mr-3 no-underline"><span>Contact Sales</span></a>
 
 ## Further reading
 

content/copilot/get-started/plans.md

@@ -45,10 +45,10 @@ Start using {% data variables.product.prodname_copilot_short %} by signing up fo
 
 * **{% data variables.copilot.copilot_student %}** — Get access to {% data variables.product.prodname_copilot_short %}'s premium features for free. [Access {% data variables.copilot.copilot_student %}](/copilot/how-tos/manage-your-account/free-access-with-copilot-student).
 
-* **{% data variables.copilot.copilot_pro_short %}** — Get unlimited completions and access to premium models. Includes a free 30-day trial for eligible users. [Try {% data variables.copilot.copilot_pro_short %} for free](https://github.com/github-copilot/signup?ref_product=copilot&ref_type=trial&ref_style=text&ref_plan=pro).
+* **{% data variables.copilot.copilot_pro_short %}** — Get unlimited completions and access to premium models. [Subscribe to {% data variables.copilot.copilot_pro_short %}](https://github.com/github-copilot/signup?ref_product=copilot&ref_type=purchase&ref_style=text&ref_plan=pro).
 
 * **{% data variables.copilot.copilot_pro_plus_short %}** — Unlock advanced AI models, extended request limits, and extra capabilities. [Subscribe to {% data variables.copilot.copilot_pro_plus_short %}](https://github.com/github-copilot/signup?ref_product=copilot&ref_type=purchase&ref_style=text&ref_plan=pro).
 
-* **{% data variables.copilot.copilot_business_short %}** — For teams and organizations. [Subscribe to {% data variables.copilot.copilot_business_short %}](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button&ref_plan=business).
+* **{% data variables.copilot.copilot_business_short %}** — For teams and organizations. [Contact Sales](https://github.com/enterprise/contact?ref_product=copilot&ref_type=engagement&ref_style=text).
 
-* **{% data variables.copilot.copilot_enterprise_short %}** — For enterprises that need advanced features and centralized management. [Subscribe to {% data variables.copilot.copilot_enterprise_short %}](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button&ref_plan=enterprise).
+* **{% data variables.copilot.copilot_enterprise_short %}** — For enterprises that need advanced features and centralized management. [Contact Sales](https://github.com/enterprise/contact?ref_product=copilot&ref_type=engagement&ref_style=text).