Skip to content

Commit b1c6ca2

Browse files
authored
Merge pull request #35622 from github/repo-sync
Repo sync
2 parents 3d48e50 + 6c7a301 commit b1c6ca2

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

content/code-security/code-scanning/managing-your-code-scanning-configuration/set-code-scanning-merge-protection.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,14 +15,17 @@ topics:
1515
## About using rulesets for {% data variables.product.prodname_code_scanning %} merge protection
1616

1717
> [!NOTE]
18-
> * This feature is currently in {% data variables.release-phases.public_preview %} and subject to change.
1918
> * Merge protection with rulesets is not related to status checks. For more information about status checks, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)."
2019
> * Merge protection with rulesets will not apply to merge queue groups or {% data variables.product.prodname_dependabot %} pull requests analyzed by default setup.
2120
2221
You can use rulesets to prevent pull requests from being merged when one of the following conditions is met:
2322

2423
{% data reusables.code-scanning.merge-protection-rulesets-conditions %}
2524

25+
Typically you should use rulesets target long-lived feature branches, where you would like to guarantee that code has been analyzed before pull requests can be merged.
26+
27+
Configuring a {% data variables.product.prodname_code_scanning %} rule will not automatically enable {% data variables.product.prodname_code_scanning %}. For more information about how to enable code scanning, see "[AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning)."
28+
2629
For more information about {% data variables.product.prodname_code_scanning %} alerts, see "[AUTOTITLE](/code-security/code-scanning/managing-code-scanning-alerts/about-code-scanning-alerts)."
2730

2831
You can set merge protection with rulesets at the repository {% ifversion ghec or ghes %}or organization levels{% else %}level{% endif %}, and for repositories configured with either default setup or advanced setup. You can also use the REST API to set merge protection with rulesets.

0 commit comments

Comments
 (0)