Fix sections in the "Configure dependabot.yml" docs being affected by a recent unrelated change. #27866
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why:
Closes: #27863
What's being changed (if available, include any code snippets, screenshots, or gifs):
A recent commit, 7b8fd5e, updated the
reusables.dependabot.option-affects-security-updates
template. This had the intended affect of updating the section being edited, but had a (presumably) unintended side-effect of affecting all other sections that used that template.This PR reverts the changes to the
reusables.dependabot.option-affects-security-updates
, sparing all other sections that received the unintended change, while moving the originally-intended content directly to the section it was intended for.Before this PR:
After:
Check off the following:
I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.
data
directory.For content changes, I have completed the self-review checklist.