Merge pull request #43292 from github/repo-sync

Repo sync

Author: docs-bot

content/account-and-profile/how-tos/organization-membership/publicizing-or-hiding-organization-membership.md

@@ -1,6 +1,6 @@
 ---
 title: Publicizing or hiding organization membership
-intro: Show avatars for organizations where you’re an organization member.
+intro: Show avatars for organizations where you're an organization member.
 redirect_from:
   - /articles/publicizing-or-concealing-organization-membership
   - /articles/publicizing-or-hiding-organization-membership

content/actions/reference/workflows-and-actions/metadata-syntax.md

@@ -1,7 +1,7 @@
 ---
 title: Metadata syntax reference
 shortTitle: Metadata syntax
-intro: You can create actions to perform tasks in your repository. If you’re making a custom action, it will require a metadata file that uses YAML syntax.
+intro: You can create actions to perform tasks in your repository. If you're making a custom action, it will require a metadata file that uses YAML syntax.
 redirect_from:
   - /articles/metadata-syntax-for-github-actions
   - /github/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions

content/code-security/concepts/code-scanning/about-code-scanning-alerts.md

@@ -40,7 +40,7 @@ With a {% data variables.copilot.copilot_enterprise %} license, you can also ask
 
 {% ifversion security-overview-org-codeql-pr-alerts %}
 
-For {% data variables.product.prodname_code_scanning %} alerts from {% data variables.product.prodname_codeql %} analysis, you can use security overview to see how {% data variables.product.prodname_codeql %} is performing in pull requests in repositories across your organization, and to identify repositories where you may need to take action. For more information, see [AUTOTITLE](/code-security/security-overview/viewing-metrics-for-pull-request-alerts).
+For {% data variables.product.prodname_code_scanning %} alerts from {% data variables.product.prodname_codeql %} analysis, you can use security overview to see how {% data variables.product.prodname_codeql %} is performing in pull requests in repositories across your organization, and to identify repositories where you may need to take action. For more information, see [AUTOTITLE](/code-security/concepts/code-scanning/pull-request-alert-metrics).
 
 {% endif %}
 

content/code-security/concepts/code-scanning/index.md

@@ -23,4 +23,5 @@ children:
   - /multi-repository-variant-analysis
   - /codeql
   - /tool-status-page
+  - /pull-request-alert-metrics
 ---

content/code-security/concepts/code-scanning/pull-request-alert-metrics.md

@@ -0,0 +1,59 @@
+---
+title: CodeQL pull request alert metrics
+shortTitle: Pull request alert metrics
+intro: Understand {% data variables.product.prodname_codeql %}'s performance in pull requests across your organizations.
+permissions: '{% data reusables.permissions.security-overview %}'
+product: '{% data reusables.gated-features.security-overview-fpt-cs-only %}'
+topics:
+  - Security overview
+  - Code Security
+  - Code scanning
+  - CodeQL
+  - Organizations
+  - Teams
+contentType: concepts
+versions:
+  feature: security-overview-org-codeql-pr-alerts
+---
+
+## Overview
+
+The metrics overview for {% data variables.product.prodname_codeql %} pull request alerts on security overview helps you understand how well {% data variables.product.prodname_codeql %} is preventing vulnerabilities in pull requests in your organization or across organizations in your enterprise. You can view the entire dataset or filter for specific criteria, making it easy to identify repositories where you may need to take action to find and reduce security risks.
+
+## Available metrics
+
+The overview shows you a summary of how many vulnerabilities prevented by {% data variables.product.prodname_codeql %} have been caught in pull requests. The metrics are only tracked for pull requests that have been merged into the default branches of repositories in your organizations.
+
+You can also find more granular metrics, such as how many alerts were fixed{% ifversion code-scanning-autofix %} with and without {% data variables.copilot.copilot_autofix_short %} suggestions{% endif %}, how many were unresolved and merged, and how many were dismissed as false positive or risk accepted.
+
+You can also view:
+
+* The rules that are causing the most alerts, and how many alerts each rule is associated with.
+
+* The number of alerts that were merged into the default branch without resolution, and the number of alerts dismissed as an acceptable risk.
+
+{% ifversion code-scanning-autofix %}
+* The number of alerts that were fixed with an accepted {% data variables.copilot.copilot_autofix_short %} suggestion, displayed as a fraction of how many total {% data variables.copilot.copilot_autofix_short %} suggestions were available.
+
+* Remediation rates, in a graph showing the percentage of alerts that were remediated with an available {% data variables.copilot.copilot_autofix_short %} suggestion, and the percentage of alerts that were remediated without a {% data variables.copilot.copilot_autofix_short %} suggestion.
+
+* Mean time to remediate, in a graph showing the average age of closed alerts that were remediated with an available {% data variables.copilot.copilot_autofix_short %} suggestion, and the average age of closed alerts that were remediated without a {% data variables.copilot.copilot_autofix_short %} suggestion.
+{% endif %}
+
+{% ifversion code-scanning-autofix %}
+> [!NOTE] Metrics for {% data variables.copilot.copilot_autofix_short %} will be shown only for repositories where {% data variables.copilot.copilot_autofix_short %} is enabled.
+{% else %}
+> [!NOTE] Metrics for {% data variables.copilot.copilot_autofix_short %} are omitted because {% data variables.copilot.copilot_autofix_short %} is available only on {% data variables.product.github %} cloud platforms.
+{% endif %}
+
+## Visibility
+
+You can see {% data variables.product.prodname_code_scanning %} metrics for a repository if you have:
+
+* The `admin` role for the repository
+* A custom repository role with the "View {% data variables.product.prodname_code_scanning %} alerts" fine-grained permissions for the repository
+* Access to alerts for the repository
+
+## Next steps
+
+To find your pull request alert metrics, see [AUTOTITLE](/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-pull-request-alerts).

content/code-security/concepts/secret-security/index.md

@@ -21,6 +21,7 @@ children:
   - /about-bypass-requests-for-push-protection
   - /about-secret-scanning-for-partners
   - /github-secret-types
+  - /push-protection-metrics
   - /push-protection-from-the-command-line
   - /working-with-push-protection-and-the-github-mcp-server
   - /working-with-push-protection-from-the-rest-api

content/code-security/concepts/secret-security/push-protection-metrics.md

@@ -0,0 +1,44 @@
+---
+title: Secret scanning push protection metrics
+shortTitle: Push protection metrics
+intro: 'Understand push protection''s performance across your organizations.'
+permissions: '{% data reusables.permissions.security-overview %}'
+product: '{% data reusables.gated-features.security-overview-fpt-sp-only %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Security overview
+  - Secret Protection
+  - Secret scanning
+  - Organizations
+  - Teams
+contentType: concepts
+---
+
+## Overview
+
+The metrics overview for {% data variables.product.prodname_secret_scanning %} push protection on security overview helps you understand how well you are preventing secret leaks in your organization or across organizations in your enterprise. You can view the entire dataset or filter for specific criteria, making it easy to identify repositories where you may need to take action to prevent future leaks.
+
+## Available metrics
+
+The overview shows you a summary of how many pushes containing secrets have been successfully blocked by push protection, as well as how many times push protection was bypassed.
+
+You can also find more granular metrics, such as:
+* The secret types that have been blocked or bypassed the most
+* The repositories that have had the most pushes blocked
+* The repositories that are bypassing push protection the most
+* The percentage distribution of reasons that users give when they bypass the protection
+
+## Visibility
+
+You can see {% data variables.product.prodname_secret_scanning %} metrics for a repository if you have:
+
+* The `admin` role for the repository
+* A custom repository role with the "View {% data variables.product.prodname_secret_scanning %} alerts" fine-grained permissions for the repository
+* Access to alerts for the repository
+
+## Next steps
+
+To find your push protection metrics, see [AUTOTITLE](/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-secret-scanning-push-protection).

content/code-security/concepts/vulnerability-reporting-and-management/about-your-exposure-to-vulnerabilities-in-your-code-and-in-dependencies.md

@@ -1,7 +1,7 @@
 ---
 title: About exposure to vulnerabilities in your code and in dependencies
 shortTitle: Vulnerability exposure
-intro: Understand how vulnerabilities in your own code and in third-party dependencies contribute to your organization’s overall security exposure, and how to measure and reduce that risk.
+intro: Understand how vulnerabilities in your own code and in third-party dependencies contribute to your organization's overall security exposure, and how to measure and reduce that risk.
 allowTitleToDifferFromFilename: true
 product: '{% data reusables.gated-features.ghas-billing %}'
 versions:

content/code-security/how-tos/manage-security-alerts/manage-code-scanning-alerts/assessing-code-scanning-alerts-for-your-repository.md

@@ -58,7 +58,7 @@ With a {% data variables.copilot.copilot_enterprise %} license, you can ask {% d
 
 ## Viewing metrics for {% data variables.product.prodname_codeql %} pull request alerts for an organization
 
-For {% data variables.product.prodname_code_scanning %} alerts from {% data variables.product.prodname_codeql %} analysis, you can use security overview to see how {% data variables.product.prodname_codeql %} is performing in pull requests in repositories where you have write access across your organization, and to identify repositories where you may need to take action. For more information, see [AUTOTITLE](/code-security/security-overview/viewing-metrics-for-pull-request-alerts).
+For {% data variables.product.prodname_code_scanning %} alerts from {% data variables.product.prodname_codeql %} analysis, you can use security overview to see how {% data variables.product.prodname_codeql %} is performing in pull requests in repositories where you have write access across your organization, and to identify repositories where you may need to take action. For more information, see [AUTOTITLE](/code-security/concepts/code-scanning/pull-request-alert-metrics).
 
 {% endif %}
 

content/code-security/how-tos/secure-at-scale/configure-enterprise-security/manage-your-coverage/index.md

@@ -1,6 +1,6 @@
 ---
 title: Manage your coverage
-intro: Review and manage your enterprise’s repository security coverage by adjusting which repositories are included in your custom security configurations and removing unneeded configurations.
+intro: Review and manage your enterprise's repository security coverage by adjusting which repositories are included in your custom security configurations and removing unneeded configurations.
 versions:
   fpt: '*'
   ghes: '*'