From ff3fe320b410b85903b8857ba47172f0d8f0d943 Mon Sep 17 00:00:00 2001 From: Spcial24 Date: Sun, 29 Jun 2025 01:47:38 +0530 Subject: [PATCH] Revert "Repo sync" --- .../secret-scanning/introduction/about-push-protection.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/code-security/secret-scanning/introduction/about-push-protection.md b/content/code-security/secret-scanning/introduction/about-push-protection.md index f0808ead500d..fea81dede0ee 100644 --- a/content/code-security/secret-scanning/introduction/about-push-protection.md +++ b/content/code-security/secret-scanning/introduction/about-push-protection.md @@ -74,6 +74,8 @@ By default, anyone with write access to the repository can choose to bypass push * **Efficient secret management:** Instead of retrospectively dealing with exposed secrets, developers can address issues at the source. This makes secret management more efficient and less time-consuming. +* **Integration with CI/CD pipelines:** Push Protection can be integrated into your Continuous Integration/Continuous Deployment (CI/CD) pipelines, ensuring that every push is scanned for secrets before it gets deployed. This adds an extra layer of security to your DevOps practices. + * **Ability to detect custom patterns:** Organizations can define custom patterns for detecting secrets unique to their environment. This customization ensures that push Protection can effectively identify and block even non-standard secrets. {% ifversion push-protection-delegated-bypass %}* **Delegated bypass for flexibility:** For cases where false positives occur or when certain patterns are necessary, the delegated bypass feature allows designated users to approve specific pushes. This provides flexibility without compromising overall security.{% endif %} @@ -88,6 +90,10 @@ Every user across {% data variables.product.prodname_dotcom %} can also enable p Once push protection is enabled, you can customize it further: +### Integrate with CI/CD pipelines + +Integrate push protection with your Continuous Integration/Continuous Deployment (CI/CD) pipelines to ensure that it runs scans during automated processes. This typically involves adding steps in your pipeline configuration file to call GitHub's APIs or using {% data variables.product.prodname_actions %}. + ### Define custom patterns Define custom patterns that push protection can use to identify secrets and block pushes containing these secrets. For more information, see [AUTOTITLE](/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/custom-patterns/defining-custom-patterns-for-secret-scanning).