We somehow overlooked this article when the security teams overhauled the options for configuring these features.
My current understanding is:
Security updates can be enabled/disabled at the repository and organization level.
Security updates are only automatically enabled when you create a new repository in an organization that has set up Automatically enable for new repositories
Security updates are automatically disabled if you create a fork of a repository that has security updates enabled, so that you can make your own choice about whether to enable security updates or not on the fork. This is true even for organizations that have Automatically enable for new repositories turned on (see https://github.com/github/docs-content/issues/6575#issuecomment-1074039507).
Security updates are automatically disabled when you archive a repository.
We need to go through the above MS Learn module and make sure that our content reflects the changes mentioned. Below are the updated docs sections that have the up-to-date content.
This is a tracking issue in response to https://github.com/github/docs-content/issues/6575
What is the MS Learn module affected?
Describe the desired content changes
We somehow overlooked this article when the security teams overhauled the options for configuring these features.
My current understanding is:
Resources
Action items
We need to go through the above MS Learn module and make sure that our content reflects the changes mentioned. Below are the updated docs sections that have the up-to-date content.