Remove leftover map topic (follow up PR) (#19517)
This commit is contained in:
@@ -3,6 +3,8 @@ title: About securing your repository
|
||||
intro: '{% data variables.product.product_name %} provides a number of ways that you can help keep your repository secure.'
|
||||
redirect_from:
|
||||
- /github/administering-a-repository/about-securing-your-repository
|
||||
- /articles/securing-your-repository
|
||||
- /github/administering-a-repository/securing-your-repository
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=3.0'
|
||||
|
||||
@@ -14,5 +14,4 @@ children:
|
||||
- /configuring-pull-request-merges
|
||||
- /defining-the-mergeability-of-pull-requests
|
||||
- /releasing-projects-on-github
|
||||
- /securing-your-repository
|
||||
---
|
||||
|
||||
@@ -1,14 +0,0 @@
|
||||
---
|
||||
title: Securing your repository
|
||||
intro: 'Security features like {% data variables.product.prodname_secret_scanning %} protect your repository''s data.'
|
||||
mapTopic: true
|
||||
redirect_from:
|
||||
- /articles/securing-your-repository
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=3.0'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- Repositories
|
||||
---
|
||||
|
||||
@@ -7,6 +7,6 @@ versions:
|
||||
|
||||
{% data reusables.secret-scanning.api-beta %}
|
||||
|
||||
The {% data variables.product.prodname_secret_scanning %} API lets you retrieve and update secret scanning alerts from a private repository. For more information on secret scanning for private repositories, see "[Securing your repository](/github/administering-a-repository/securing-your-repository)."
|
||||
The {% data variables.product.prodname_secret_scanning %} API lets you retrieve and update secret scanning alerts from a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information on secret scanning, see "[About secret scanning](/code-security/secret-security/about-secret-scanning)."
|
||||
|
||||
{% include rest_operations_at_current_path %}
|
||||
|
||||
Reference in New Issue
Block a user