Fix broken GHES 3.20 link in enabling-extended-metadata-checks-for-your-repository.md (#60396)

Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>

Author: jc-clark

content/code-security/how-tos/secure-your-secrets/customize-leak-detection/enabling-extended-metadata-checks-for-your-repository.md

@@ -17,10 +17,14 @@ redirect_from:
 
 This article shows how you can enable extended metadata checks for individual repositories through repository settings. Alternatively, you can enable them at scale using **security configurations** at the organization or enterprise level. See [AUTOTITLE](/code-security/how-tos/secure-at-scale/configure-organization-security/establish-complete-coverage/creating-a-custom-security-configuration) or [AUTOTITLE](/code-security/how-tos/secure-at-scale/configure-enterprise-security/establish-complete-coverage/creating-a-custom-security-configuration-for-your-enterprise).
 
+{% ifversion secret-scanning-validity-check-partner-patterns %}
+
 ## Prerequisites
 
 Before enabling metadata checks, you need to ensure that validity checks are enabled for the repository. See [AUTOTITLE](/code-security/secret-scanning/enabling-secret-scanning-features/enabling-validity-checks-for-your-repository#enabling-validity-checks).
 
+{% endif %}
+
 ## Enabling extended metadata checks
 
 {% ifversion fpt or ghec %}