Skip to content

Commit 22c74a3

Browse files
Remove unsupported CI/CD Integration (#56371)
1 parent c0babd8 commit 22c74a3

File tree

1 file changed

+0
-6
lines changed

1 file changed

+0
-6
lines changed

content/code-security/secret-scanning/introduction/about-push-protection.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -74,8 +74,6 @@ By default, anyone with write access to the repository can choose to bypass push
7474

7575
* **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.
7676

77-
* **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.
78-
7977
* **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.
8078

8179
{% 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 %}
@@ -90,10 +88,6 @@ Every user across {% data variables.product.prodname_dotcom %} can also enable p
9088

9189
Once push protection is enabled, you can customize it further:
9290

93-
### Integrate with CI/CD pipelines
94-
95-
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 %}.
96-
9791
### Define custom patterns
9892

9993
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).

0 commit comments

Comments
 (0)