docs: clarify usage of docs-infra scope in commit messages (#63799)

damiansire · thePunderWoman · commit 002699bcef1f · 2025-09-15T15:33:15.000Z
The contribution guide is updated to provide clearer instructions on when to use the `docs-infra` scope versus the `docs` type. This change helps contributors understand that `docs-infra` should only be used for infrastructure-related changes (application code, tooling, configuration) within the `/adev` directory. For simple content modifications, such as editing a `.md` file, `docs` without a scope is the correct choice. PR Close #63799
diff --git a/contributing-docs/commit-message-guidelines.md b/contributing-docs/commit-message-guidelines.md
@@ -96,7 +96,7 @@ There are currently a few exceptions to the "use package name" rule:
 
 * `dev-infra`: used for dev-infra related changes within the directories /scripts and /tools
 
-* `docs-infra`: used for docs-app (angular.dev) related changes within the /adev directory of the repo
+* `docs-infra`: used for infrastructure changes to the docs-app (angular.dev) within the `/adev` directory, such as application code, tooling, or configuration. **For modifications to documentation content (e.g., editing a `.md` file), use `docs:` without a scope instead.**
 
 * `migrations`: used for changes to the `ng update` migrations.
 
