fix: dependabot commit config

[gagan-bhullar-tech]

Why:

Closes: #33996

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

• I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

  • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

• For content changes, I have completed the self-review checklist.

[github-actions]

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md	fpt ghec ghes@ 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.13 3.12 3.11 3.10

---

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

[janbrasna]

The confusion comes from the example:

docs/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md

Lines 419 to 431 in 8898e15

	- package-ecosystem: "pip"
	directory: "/"
	schedule:
	interval: "weekly"
	# Include a list of updated dependencies
	# with a prefix determined by the dependency group
	commit-message:
	prefix: "pip prod"
	prefix-development: "pip dev"
	include: "scope"
	```
	If you use the same configuration as in the example above, bumping the `requests` library in the `pip` development dependency group will generate a commit message of:

where a) the scope is not being shown in the example below, b) is not supported by all managers in the ecosystem.

So it needs moving out of pip, and adding somewhere unambiguous. (Or, just removing L428, its demonstration is already present at Composer.)

[nguyenalex836]

@gagan-bhullar-tech Thank you for opening a PR! I'll get this triaged for review ✨

[github-actions]

Thanks for opening a pull request! We've triaged this issue for technical review by a subject matter expert 👀

[janbrasna]

Yes, thanks @gagan-bhullar-tech — this now reflects my experience. Let's just wait for the triage to xcheck the wording, but this now fixes the issue for me. The code example matches its description below w/ expected results, and the allow table looks reasonably valid.

(Note for reviewer: The removed scope in example didn't need to be moved elsewhere, as the Composer example right above it already demonstrates that.)

[gagan-bhullar-tech]

Yes, thanks @gagan-bhullar-tech — this now reflects my experience. Let's just wait for the triage to xcheck the wording, but this now fixes the issue for me. The code example matches its description below w/ expected results, and the allow table looks reasonably valid.

(Note for reviewer: The removed scope in example didn't need to be moved elsewhere, as the Composer example right above it already demonstrates that.)

thanks @janbrasna for reviewing the PR.

[github-actions]

Thanks for opening a pull request! We've triaged this issue for technical review by a subject matter expert 👀

[jakecoffman]

reviewed for technical accuracy

[mchammer01]

LGTM from an editorial point of view 💖

Thank you @janbrasna for spotting the problem and the inaccuracies, and @gagan-bhullar-tech for fixing the docs ✨

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡