Skip to content

Commit 40c32fc

Browse files
sabrowning1mchammer01panoslith
authored
Re-add info on preserving default repo settings for security configs (#59604)
Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com> Co-authored-by: Panagiotis Lithadiotis <55960073+panoslith@users.noreply.github.com>
1 parent b5ca26d commit 40c32fc

1 file changed

Lines changed: 10 additions & 0 deletions

File tree

content/code-security/concepts/security-at-scale/security-configurations.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -87,6 +87,16 @@ Some situations can break the enforcement of {% data variables.product.prodname_
8787
* Self-hosted runners with the label `code-scanning` are not available.{% endif %}
8888
* The languages excluded from {% data variables.product.prodname_code_scanning %} default setup are changed at the repository level.
8989

90+
{% ifversion security-configuration-enterprise-level %}
91+
92+
## Preservation of default settings for new repositories
93+
94+
If you had default security settings in place for newly created repositories, {% data variables.product.github %} will preserve these settings by automatically creating a "New repository default settings" {% data variables.product.prodname_security_configuration %} for your enterprise. The configuration matches your previous enterprise-level default settings for new repositories as of December 2024.
95+
96+
The configuration will be automatically applied to any newly created repositories in your enterprise that do not belong to an organization with its own default settings.
97+
98+
{% endif %}
99+
90100
## Next steps
91101

92102
{% ifversion security-configurations-cloud %}

0 commit comments

Comments
 (0)