Merge pull request #42506 from github/repo-sync

Repo sync

Author: docs-bot

content/admin/monitoring-and-managing-your-instance/monitoring-your-instance/about-the-monitor-dashboards.md

@@ -43,7 +43,7 @@ Within the pre-built dashboards you can find various sections grouping graphs of
 
 {% ifversion ghes-opentelemetry %}
 
-If you have enabled metrics for OpenTelemetry, then additional dashboards are available, see: [AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/enable-advanced-dashboards).
+If you have enabled metrics for OpenTelemetry, then additional dashboards are available, see: [AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/advanced-dashboards).
 
 {% endif %}
 

content/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/about-opentelemetry-metrics.md

@@ -35,7 +35,7 @@ OpenTelemetry metrics offer several advantages over the legacy collectd system:
 * **Extensible**: Support for custom metrics and external monitoring integrations
 * **Native endpoints**: Direct integration with service `/metrics` endpoints for efficient monitoring
 
-With OpenTelemetry, advanced Grafana dashboards with enhanced visualization and monitoring capabilities are available, see: [AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/enable-advanced-dashboards).
+With OpenTelemetry, advanced Grafana dashboards with enhanced visualization and monitoring capabilities are available, see: [AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/advanced-dashboards).
 
 ## Key components
 

…ry-metrics/enable-advanced-dashboards.md …telemetry-metrics/advanced-dashboards.mdcontent/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/enable-advanced-dashboards.md renamed to content/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/advanced-dashboards.md content/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/enable-advanced-dashboards.md renamed to content/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/advanced-dashboards.md

@@ -1,6 +1,8 @@
 ---
-title: Enabling advanced dashboards of OpenTelemetry metrics
+title: Advanced dashboards of OpenTelemetry metrics
 intro: 'After enabling OpenTelemetry metrics collection on your {% data variables.product.prodname_ghe_server %} instance, you have access to additional dashboards with enhanced visualization and monitoring capabilities.'
+redirect_from:
+  - /enterprise/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/enable-advanced-dashboards
 versions:
   feature: ghes-opentelemetry
 topics:
@@ -10,7 +12,7 @@ topics:
   - Monitoring
   - Performance
 type: how_to
-shortTitle: Enable advanced dashboards
+shortTitle: Advanced dashboards
 ---
 
 {% data reusables.enterprise.opentelemetry-migration %}
@@ -21,9 +23,18 @@ shortTitle: Enable advanced dashboards
 
 {% endif %}
 
+## Prerequisites
+
+* OpenTelemetry metrics are enabled for your {% data variables.product.prodname_ghe_server %} instance
+
+
 ## Additional dashboards
 
+{% ifversion ghes < 3.19 %}
 When OpenTelemetry metrics are enabled, you can turn on advanced Grafana dashboards with enhanced visualization and monitoring capabilities.
+{% else %}
+When OpenTelemetry metrics are enabled, you will have access to advanced Grafana dashboards with enhanced visualization and monitoring capabilities.
+{% endif %}
 
 * **Elasticsearch** - Detailed metrics for search performance, indexing operations, and cluster health
 * **Nomad** - In-depth monitoring of job scheduling, resource allocation, and service orchestration
@@ -33,12 +44,15 @@ When OpenTelemetry metrics are enabled, you can turn on advanced Grafana dashboa
 
 These dashboards provide more granular insights into your {% data variables.product.prodname_ghe_server %} instance's performance and can help with advanced troubleshooting and capacity planning.
 
-## Prerequisites
+{% ifversion ghes < 3.19 %}
+## Enabling advanced dashboards
+
+### Prerequisites
 
-* OpenTelemetry metrics are enabled for your {% data variables.product.prodname_ghe_server %} instance
 * SSH access to your {% data variables.product.prodname_ghe_server %} instance
 
-## Enabling advanced dashboards
+---
+
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
 1. Run the following command to enable advanced dashboards:
@@ -50,3 +64,4 @@ These dashboards provide more granular insights into your {% data variables.prod
 {% data reusables.enterprise.apply-configuration %}
 
 After running these commands, your external Grafana instance will have access to additional pre-configured dashboards.
+{% endif %}

content/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/configuring-opentelemetry-for-your-instance.md

@@ -169,5 +169,5 @@ sudo journalctl -u victoriametrics -f
 
 ## Next steps
 
-* To enable advanced monitoring dashboards, see [AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/enable-advanced-dashboards)
+* To enable advanced monitoring dashboards, see [AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/advanced-dashboards)
 * To set up external monitoring, see [AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/setting-up-external-monitoring-with-opentelemetry).

content/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/index.md

@@ -8,7 +8,7 @@ topics:
 children:
   - /about-opentelemetry-metrics
   - /configuring-opentelemetry-for-your-instance
-  - /enable-advanced-dashboards
+  - /advanced-dashboards
   - /setting-up-external-monitoring-with-opentelemetry
 shortTitle: OpenTelemetry metrics
 ---

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

@@ -34,21 +34,31 @@ contentType: concepts
 
 {% data variables.product.prodname_dependabot %} takes the effort out of maintaining your dependencies. You can use it to ensure that your repository automatically keeps up with the latest releases of the packages and applications it depends on.
 
-{% data reusables.dependabot.dependabot-updates-supported-repos-ecosystems %}
+{% data reusables.dependabot.pull-request-security-vs-version-updates %}
+
+You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a `dependabot.yml` configuration file into your repository.
+
+{% data reusables.dependabot.dependabot-tos %}
+
+## Updates for packages
 
-You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a `dependabot.yml` configuration file into your repository. The configuration file specifies the location of the manifest, or of other package definition files, stored in your repository. {% data variables.product.prodname_dependabot %} uses this information to check for outdated packages and applications. {% data variables.product.prodname_dependabot %} determines if there is a new version of a dependency by looking at the semantic versioning ([semver](https://semver.org/)) of the dependency to decide whether it should update to that version. For certain package managers, {% data variables.product.prodname_dependabot_version_updates %} also supports vendoring. Vendored (or cached) dependencies are dependencies that are checked in to a specific directory in a repository rather than referenced in a manifest. Vendored dependencies are available at build time even if package servers are unavailable. {% data variables.product.prodname_dependabot_version_updates %} can be configured to check vendored dependencies for new versions and update them if necessary.
+The `dependabot.yml` configuration file specifies the location of the manifest, or of other package definition files, stored in your repository. {% data variables.product.prodname_dependabot %} uses this information to check for outdated packages and applications. {% data variables.product.prodname_dependabot %} determines if there is a new version of a dependency by looking at the semantic versioning ([semver](https://semver.org/)) of the dependency to decide whether it should update to that version. {% data reusables.dependabot.dependabot-updates-supported-repos-ecosystems %}
+
+For certain package managers, {% data variables.product.prodname_dependabot_version_updates %} also supports vendoring. Vendored (or cached) dependencies are dependencies that are checked in to a specific directory in a repository rather than referenced in a manifest. Vendored dependencies are available at build time even if package servers are unavailable. {% data variables.product.prodname_dependabot_version_updates %} can be configured to check vendored dependencies for new versions and update them if necessary.
 
 When {% data variables.product.prodname_dependabot %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. For vendored dependencies, {% data variables.product.prodname_dependabot %} raises a pull request to replace the outdated dependency with the new version directly. You check that your tests pass, review the changelog and release notes included in the pull request summary, and then merge it. For more information, see [AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates).
 
 If you enable _security updates_, {% data variables.product.prodname_dependabot %} also raises pull requests to update vulnerable dependencies. For more information, see [AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates).
 
-{% data reusables.dependabot.pull-request-security-vs-version-updates %}
+## Updates for actions
 
-{% data reusables.dependabot.dependabot-updates-signed-commits %}
+Actions are often updated with bug fixes and new features to make automated processes more reliable, faster, and safer. When you enable {% data variables.product.prodname_dependabot_version_updates %} for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %} will help ensure that references to actions in a repository's _workflow.yml_ file and reusable workflows used inside workflows are kept up to date.
 
-{% data reusables.dependabot.dependabot-updates-prs-and-actions %}
+For each action in the file, {% data variables.product.prodname_dependabot %} checks the action's reference (typically a version number or commit identifier associated with the action) against the latest version. If a more recent version of the action is available, {% data variables.product.prodname_dependabot %} will send you a pull request that updates the reference in the workflow file to the latest version.
 
-{% data reusables.dependabot.dependabot-tos %}
+{% data variables.product.prodname_dependabot %} also checks workflow files for uses of reusable workflows, and updates the Git reference for these called reusable workflows.
+
+To enable this feature, see [AUTOTITLE](/code-security/how-tos/secure-your-supply-chain/secure-your-dependencies/keeping-your-actions-up-to-date-with-dependabot).
 
 ## Frequency of {% data variables.product.prodname_dependabot %} pull requests
 

content/code-security/how-tos/secure-your-supply-chain/secure-your-dependencies/keeping-your-actions-up-to-date-with-dependabot.md

@@ -23,27 +23,10 @@ contentType: how-tos
 
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-## About {% data variables.product.prodname_dependabot_version_updates %} for actions
-
-Actions are often updated with bug fixes and new features to make automated processes more reliable, faster, and safer. When you enable {% data variables.product.prodname_dependabot_version_updates %} for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %} will help ensure that references to actions in a repository's _workflow.yml_ file and reusable workflows used inside workflows are kept up to date.
-
-For each action in the file, {% data variables.product.prodname_dependabot %} checks the action's reference (typically a version number or commit identifier associated with the action) against the latest version. For information about how action creators version their actions, see [Using release management for your custom actions](/actions/learn-github-actions/finding-and-customizing-actions#using-release-management-for-your-custom-actions).
-
-If a more recent version of the action is available, {% data variables.product.prodname_dependabot %} will send you a pull request that updates the reference in the workflow file to the latest version. For more information about {% data variables.product.prodname_dependabot_version_updates %}, see [AUTOTITLE](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates). For more information about configuring workflows for {% data variables.product.prodname_actions %}, see [AUTOTITLE](/actions/learn-github-actions).
-
-{% data variables.product.prodname_dependabot %} also checks workflow files for uses of reusable workflows, and updates the git reference for these called reusable workflows. For more information about reusable workflows, see [AUTOTITLE](/actions/using-workflows/reusing-workflows).
-
-{% ifversion fpt or ghec %}
-
-> [!NOTE]
-> {% data reusables.actions.workflow-runs-dependabot-note %}
-
-{% endif %}
+When you enable {% data variables.product.prodname_dependabot_version_updates %} for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %} will help ensure that references to actions in a repository's _workflow.yml_ file and reusable workflows used inside workflows are kept up to date. For more information, see [AUTOTITLE](/code-security/concepts/supply-chain-security/about-dependabot-version-updates).
 
 ## Enabling {% data variables.product.prodname_dependabot_version_updates %} for actions
 
-You can configure {% data variables.product.prodname_dependabot_version_updates %} to maintain your actions as well as the libraries and packages you depend on.
-
 1. If you have already enabled {% data variables.product.prodname_dependabot_version_updates %} for other ecosystems or package managers, simply open the existing `dependabot.yml` file. Otherwise, create a `dependabot.yml` configuration file in the `.github` directory of your repository. For more information, see [AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates).
 1. Specify `"github-actions"` as a `package-ecosystem` to monitor.
 1. Set the `directory` to `"/"` to check for workflow files in `.github/workflows`.
@@ -52,7 +35,7 @@ You can configure {% data variables.product.prodname_dependabot_version_updates
 
 You can also enable {% data variables.product.prodname_dependabot_version_updates %} on forks. For more information, see [AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-version-updates-on-forks).
 
-### Example `dependabot.yml` file for {% data variables.product.prodname_actions %}
+## Example `dependabot.yml` file for {% data variables.product.prodname_actions %}
 
 The example `dependabot.yml` file below configures version updates for {% data variables.product.prodname_actions %}. The `directory` must be set to `"/"` to check for workflow files in `.github/workflows`. The `schedule.interval` is set to `"weekly"`. After this file has been checked in or updated, {% data variables.product.prodname_dependabot %} checks for new versions of your actions. {% data variables.product.prodname_dependabot %} will raise pull requests for version updates for any outdated actions that it finds. After the initial version updates, {% data variables.product.prodname_dependabot %} will continue to check for outdated versions of actions once a week.
 

content/code-security/reference/supply-chain-security/supported-ecosystems-and-repositories.md

@@ -18,17 +18,11 @@ redirect_from:
 contentType: reference
 ---
 
-## About {% data variables.product.prodname_dependabot %}
+This article provides reference information about the package ecosystems and repository types that {% data variables.product.prodname_dependabot %} supports.
 
-{% data variables.product.prodname_dependabot %} helps you stay on top of your dependency ecosystems. With {% data variables.product.prodname_dependabot %}, you can keep the dependencies you rely on up-to-date, addressing any potential security issues in your supply chain.
+{% data variables.product.prodname_dependabot %} is a {% data variables.product.github %} tool that helps keep your dependencies secure and up to date. It automatically detects vulnerable or outdated dependencies in your repositories and creates pull requests to update them, making it easier to maintain your software supply chain security. For more information, see [AUTOTITLE](/code-security/tutorials/secure-your-dependencies/dependabot-quickstart-guide).
 
-{% data reusables.dependabot.dependabot-overview %}
-
-For more information about {% data variables.product.prodname_dependabot %}, see [AUTOTITLE](/code-security/getting-started/dependabot-quickstart-guide).
-
-In this article, you can see what the supported ecosystems and repositories are.
-
-## Supported ecosystems and repositories
+## Supported ecosystems maintained by {% data variables.product.github %}
 <!-- If you make changes to this feature, check whether any of the changes affect languages listed in /get-started/learning-about-github/github-language-support. If so, please update the language support article accordingly. -->
 
 You can configure updates for repositories that contain a dependency manifest or lock file for one of the supported package managers. For some package managers, you can also configure vendoring for dependencies. For more information, see [`vendor`](/code-security/dependabot/working-with-dependabot/dependabot-options-reference#vendor--).

content/rest/billing/cost-centers.md

@@ -8,5 +8,12 @@ topics:
 autogenerated: rest
 allowTitleToDifferFromFilename: true
 ---
+## Required roles
+
+The following roles can access cost center API endpoints:
+
+* **Enterprise owners**
+* **Billing managers**
+* **Organization owners**
 
 <!-- Content after this section is automatically generated -->

data/reusables/actions/about-actions-usage-metrics-aggregation.md

@@ -1,4 +1,4 @@
-The time period selection feature allows you to view {% data variables.product.prodname_actions %} metrics over predefined periods, as detailed in the following table. These metrics include skipped runs and those that use zero minutes. Data is presented using Coordinated Universal Time (UTC) days.
+The time period selection feature allows you to view {% data variables.product.prodname_actions %} metrics over predefined periods, as detailed in the following table. These metrics exclude skipped runs and those that use zero minutes. Data is presented using Coordinated Universal Time (UTC) days.
 
 {% rowheaders %}