31579808f6
* New secret scanning article part 1 * Add other procedures and links * Apply suggestions from code review Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com> * UI variable suggestions Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com> * Clarify org setting and beta note * Fix GHES version * Apply suggestions from @greysteil's code review Co-authored-by: Grey Baker <greysteil@github.com> * Remove beta view restriction * Add section on regex syntax Co-authored-by: Grey Baker <greysteil@github.com> * Regex support edit Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com> Co-authored-by: Grey Baker <greysteil@github.com> Co-authored-by: Amy Burns <timeyoutakeit@github.com>
21 lines
629 B
Markdown
21 lines
629 B
Markdown
---
|
|
title: Keeping secrets secure
|
|
shortTitle: Secret security
|
|
intro: 'Let {% data variables.product.company_short %} do the hard work of ensuring that tokens, private keys, and other code secrets are not exposed in your repository.'
|
|
product: '{% data reusables.gated-features.secret-scanning %}'
|
|
versions:
|
|
free-pro-team: '*'
|
|
enterprise-server: '>=3.0'
|
|
github-ae: '*'
|
|
topics:
|
|
- Secret scanning
|
|
- Advanced Security
|
|
- Repositories
|
|
children:
|
|
- /about-secret-scanning
|
|
- /configuring-secret-scanning-for-your-repositories
|
|
- /defining-custom-patterns-for-secret-scanning
|
|
- /managing-alerts-from-secret-scanning
|
|
---
|
|
|