[2026-03-31] Rename the Security tab to Security & quality [GA] (#60482)

Co-authored-by: Joe Clark <31087804+jc-clark@users.noreply.github.com>
Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>

Author: 3 people

content/code-security/concepts/about-code-quality.md

@@ -65,7 +65,7 @@ When {% data variables.product.prodname_codeql %} finds rule-based problems on p
 
 ### Default branch results
 
-{% data variables.product.prodname_code_quality_short %} findings on the default branch are reported on "{% data variables.code-quality.code_quality_ui %}" pages on the **Security** tab for the repository:
+{% data variables.product.prodname_code_quality_short %} findings on the default branch are reported on "{% data variables.code-quality.code_quality_ui %}" pages on the **{% data variables.product.prodname_security_and_quality_tab %}** tab for the repository:
 
 * **{% data variables.code-quality.all_findings %}** shows the results of {% data variables.product.prodname_codeql %} quality analysis. See [AUTOTITLE](/code-security/code-quality/tutorials/improve-your-codebase).
 * **{% data variables.code-quality.recent_suggestions %}** shows the results of AI-powered analysis of the files most recently pushed to the default branch. See [AUTOTITLE](/code-security/code-quality/tutorials/improve-recent-merges).

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

@@ -76,7 +76,7 @@ For {% data variables.product.company_short %} to scan for non-provider patterns
 
 ## About push protection alerts
 
-Push protection scans pushes for supported secrets. If push protection detects a supported secret, it will block the push. When a contributor bypasses push protection to push a secret to the repository, a push protection alert is generated and displayed in the **Security** tab of the repository. To see all push protection alerts for a repository, you must filter by `bypassed: true` on the alerts page. For more information, see [AUTOTITLE](/code-security/how-tos/manage-security-alerts/manage-secret-scanning-alerts/viewing-alerts#filtering-alerts).
+Push protection scans pushes for supported secrets. If push protection detects a supported secret, it will block the push. When a contributor bypasses push protection to push a secret to the repository, a push protection alert is generated and displayed in the **{% data variables.product.prodname_security_and_quality_tab %}** tab of the repository. To see all push protection alerts for a repository, you must filter by `bypassed: true` on the alerts page. For more information, see [AUTOTITLE](/code-security/how-tos/manage-security-alerts/manage-secret-scanning-alerts/viewing-alerts#filtering-alerts).
 
 {% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
 

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

@@ -45,7 +45,7 @@ You can enable push protection for repositories at the repository, organization,
 * Requires {% data variables.product.prodname_GH_secret_protection_always %} to be enabled
 * Is disabled by default, and can be enabled by a repository administrator, organization owner, security manager, or enterprise owner
 * Blocks pushes containing secrets from reaching specific protected repositories
-* Generates alerts for push protection bypasses in the **Security** tab of the repository, organization, and enterprise
+* Generates alerts for push protection bypasses in the **{% data variables.product.prodname_security_and_quality_tab %}** tab of the repository, organization, and enterprise
 
 {% ifversion secret-risk-assessment %}
 

content/code-security/concepts/secret-security/about-secret-scanning-for-partners.md

@@ -23,7 +23,7 @@ category:
 
 {% data reusables.secret-scanning.what-is-scanned %}
 
-The reason partner alerts are directly sent to the secret providers whenever a leak is detected for one of their secrets is that this enables the provider to take immediate action to protect you and protect their resources. The notification process for regular alerts is different. Regular alerts are displayed on the repository's **Security** tab on {% data variables.product.prodname_dotcom %} for you to resolve.
+The reason partner alerts are directly sent to the secret providers whenever a leak is detected for one of their secrets is that this enables the provider to take immediate action to protect you and protect their resources. The notification process for regular alerts is different. Regular alerts are displayed on the repository's **{% data variables.product.prodname_security_and_quality_tab %}** tab on {% data variables.product.prodname_dotcom %} for you to resolve.
 
 {% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
 

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

@@ -40,7 +40,7 @@ When credentials like API keys and passwords are committed to repositories, they
 
 ### {% data variables.product.prodname_secret_scanning_caps %} alerts and remediation
 
-When {% data variables.product.prodname_secret_scanning %} finds a potential secret, {% data variables.product.github %} generates an alert on your repository's **Security** tab with details about the exposed credential.
+When {% data variables.product.prodname_secret_scanning %} finds a potential secret, {% data variables.product.github %} generates an alert on your repository's **{% data variables.product.prodname_security_and_quality_tab %}** tab with details about the exposed credential.
 
 When you receive an alert, rotate the affected credential immediately to prevent unauthorized access. While you can also remove secrets from your Git history, this is time-intensive and often unnecessary if you've already revoked the credential.
 

content/code-security/concepts/security-at-scale/about-security-overview.md

@@ -65,7 +65,7 @@ There are dedicated views for each type of security alert. You can limit your an
 
 The application security team at your company can use the different views for both broad and specific analyses of your organization's security status. For example, the team can use the "Overview" dashboard view to track your organization's security landscape and progression. {% ifversion pre-security-configurations %}You can also use security overview to find a set of repositories and enable or disable security features for them all at the same time. For more information, see [AUTOTITLE](/code-security/security-overview/enabling-security-features-for-multiple-repositories).{% endif %}
 
-You can find security overview on the **Security** tab for any organization. Each view shows a summary of the data that you have access to. As you add filters, all data and metrics across the view change to reflect the repositories or alerts that you've selected.
+You can find security overview on the **{% data variables.product.prodname_security_and_quality_tab %}** tab for any organization. Each view shows a summary of the data that you have access to. As you add filters, all data and metrics across the view change to reflect the repositories or alerts that you've selected.
 
 Security overview has multiple views that provide different ways to explore enablement and alert data.
 
@@ -85,7 +85,7 @@ You also create and manage security campaigns to remediate alerts from security
 
 ## About security overview for enterprises
 
-You can find security overview on the **Security** tab for your enterprise. Each page displays aggregated and repository-specific security information for your enterprise.
+You can find security overview on the **{% data variables.product.prodname_security_and_quality_tab %}** tab for your enterprise. Each page displays aggregated and repository-specific security information for your enterprise.
 
 Security overview for enterprises has multiple views that provide different ways to explore data, including an overview dashboard that visualizes alert trends. For information about the dashboard, see [AUTOTITLE](/code-security/security-overview/viewing-security-insights) and [AUTOTITLE](/code-security/reference/security-at-scale/security-overview-dashboard-metrics).
 

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

@@ -34,7 +34,7 @@ For supported ecosystems, see [AUTOTITLE](/code-security/supply-chain-security/u
 
 ## Understanding alerts
 
-When {% data variables.product.github %} detects a vulnerable dependency, a {% data variables.product.prodname_dependabot %} alert appears on the repository's **Security** tab and dependency graph. Each alert includes:
+When {% data variables.product.github %} detects a vulnerable dependency, a {% data variables.product.prodname_dependabot %} alert appears on the repository's **{% data variables.product.prodname_security_and_quality_tab %}** tab and dependency graph. Each alert includes:
 
 * A link to the affected file
 * Details about the vulnerability and its severity

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

@@ -81,7 +81,7 @@ For more information about dependency review, see [AUTOTITLE](/code-security/sup
 {% data variables.product.prodname_dependabot %} keeps your dependencies up to date by informing you of any security vulnerabilities in your dependencies and automatically opening pull requests to upgrade your dependencies. {% data variables.product.prodname_dependabot %} pull requests will target the next available secure version when a {% data variables.product.prodname_dependabot %} alert is triggered, or to the latest version when a release is published.
 
 The term "{% data variables.product.prodname_dependabot %}" encompasses the following features:
-* {% data variables.product.prodname_dependabot_alerts %}: Displayed notification on the **Security** tab for the repository, and in the repository's dependency graph. The alert includes a link to the affected file in the project, and information about a fixed version.
+* {% data variables.product.prodname_dependabot_alerts %}: Displayed notification on the **{% data variables.product.prodname_security_and_quality_tab %}** tab for the repository, and in the repository's dependency graph. The alert includes a link to the affected file in the project, and information about a fixed version.
 * {% data variables.product.prodname_dependabot_updates %}:
   * {% data variables.product.prodname_dependabot_security_updates %}: Triggered updates to upgrade your dependencies to a secure version when an alert is triggered.
   * {% data variables.product.prodname_dependabot_version_updates %}: Scheduled updates to keep your dependencies up to date with the latest version.
@@ -113,7 +113,7 @@ For more information, see [AUTOTITLE](/code-security/dependabot/working-with-dep
   * A new advisory is added to the {% data variables.product.prodname_advisory_database %}{% else %}
   * New advisory data is synchronized to your instance each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
   * The dependency graph for the repository changes
-* {% data variables.product.prodname_dependabot_alerts %} are displayed on the **Security** tab for the repository and in the repository's dependency graph. The alert includes a link to the affected file in the project, and information about a fixed version.
+* {% data variables.product.prodname_dependabot_alerts %} are displayed on the **{% data variables.product.prodname_security_and_quality_tab %}** tab for the repository and in the repository's dependency graph. The alert includes a link to the affected file in the project, and information about a fixed version.
 
 For more information, see [AUTOTITLE](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts).
 
@@ -129,7 +129,7 @@ For more information, see [AUTOTITLE](/code-security/dependabot/dependabot-alert
 * The dependency graph for a repository changes
 
 You can view {% data variables.product.prodname_dependabot_malware_alerts_short %} for a repository:
-* From the **Security** tab
+* From the **{% data variables.product.prodname_security_and_quality_tab %}** tab
 * In the dependency graph
 
 Each alert includes a link to the affected file in the project, as well as the patch version number for the package (if available).

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

@@ -24,7 +24,7 @@ Alerts are also generated when you push commits that add a known malicious packa
 
 ## Alert contents
 
-When {% data variables.product.prodname_dependabot %} detects a malicious dependency, a {% data variables.product.prodname_dependabot_malware_alert_short %} appears on the repository's **Security** tab. Each alert includes:
+When {% data variables.product.prodname_dependabot %} detects a malicious dependency, a {% data variables.product.prodname_dependabot_malware_alert_short %} appears on the repository's **{% data variables.product.prodname_security_and_quality_tab %}** tab. Each alert includes:
 
 * A link to the affected file
 * Details about the malicious package, including the package name, affected versions, and the patched version (when available)

content/code-security/getting-started/github-security-features.md

@@ -148,7 +148,7 @@ For information about how you can try {% data variables.product.prodname_GH_secr
 
 ### {% data variables.secret-scanning.user_alerts_caps %}
 
-Automatically detect tokens or credentials that have been checked into a repository. You can view alerts for any secrets that {% data variables.product.github %} finds in your code, in the **Security** tab of the repository, so that you know which tokens or credentials to treat as compromised. For more information, see [AUTOTITLE](/code-security/secret-scanning/managing-alerts-from-secret-scanning/about-alerts#about-user-alerts).
+Automatically detect tokens or credentials that have been checked into a repository. You can view alerts for any secrets that {% data variables.product.github %} finds in your code, in the **{% data variables.product.prodname_security_and_quality_tab %}** tab of the repository, so that you know which tokens or credentials to treat as compromised. For more information, see [AUTOTITLE](/code-security/secret-scanning/managing-alerts-from-secret-scanning/about-alerts#about-user-alerts).
 
 {% data reusables.advanced-security.available-for-public-repos %}