docs: exclude docs directory from pre-commit hook

[mendonk]

Exclude the docs/ directory from the detect-secrets hook, because it blocks commits and pollutes code samples if you need to add # pragma: allowlist secret.

Summary by CodeRabbit

• Chores
  • Updated secret scanning configuration to exclude the documentation directory, reducing false positives and speeding up pre-commit checks for contributors.
  • Improves developer workflow without affecting application behavior or user-facing functionality.
  • No changes to features, performance, or compatibility for end-users.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

Updated .pre-commit-config.yaml to configure the detect-secrets hook to exclude the docs/ directory from scanning by adding an exclude pattern.

Changes

Cohort / File(s)	Summary of changes
Pre-commit hooks .\pre-commit-config.yaml	Added detect-secrets hook configuration to exclude docs/ via exclude: ^docs/.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• fix: exclude docs folder from local biome check #9799 — Also modifies .pre-commit-config.yaml to exclude docs/ (for local biome-check), aligning with this PR’s exclusion pattern concept.
• chore: add detect-secrets pre-commit hook and baseline file #8655 — Adjusts the detect-secrets entry in .pre-commit-config.yaml; this PR refines it further by excluding docs/.

Suggested labels

lgtm

Suggested reviewers

• mfortman11
• aimurphy

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Excessive Mock Usage Warning	❓ Inconclusive	No test files were added or modified in this pull request, so there is no new or changed test code to evaluate for excessive mock usage, and existing repository tests remain outside the scope of this check.	Because no tests were touched, I cannot assess mock usage for this change; if there are specific test files of concern, please reference them or include related modifications so they can be reviewed.

✅ Passed checks (6 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title concisely and clearly summarizes the main change of excluding the docs directory from the pre-commit detect-secrets hook, matching the content of the changeset without any noise or ambiguity.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Test Coverage For New Implementations	✅ Passed	The PR only updates the detect-secrets configuration to exclude the docs directory and does not introduce new functionality or bug fixes, so no additional tests are required or expected; confirming the change shows no test files were added, but this is acceptable because there is nothing new to cover.
Test Quality And Coverage	✅ Passed	The PR only updates the pre-commit configuration by excluding the docs/ directory from detect-secrets scanning and does not introduce or modify runtime code or tests, so no new functionality requires coverage. Because no behavioral changes exist, there is nothing new to exercise through automated tests, and the project’s existing testing strategy remains unaffected. Therefore the test quality and coverage standards for this change are inherently satisfied.
Test File Naming And Structure	✅ Passed	No test files were added or modified in this pull request, and the existing backend and frontend test suites already adhere to the required naming patterns and structure with pytest-style test_*.py files and Playwright-focused *.test.ts/tsx files organized under their respective directories; integration tests are appropriately labeled and include meaningful, descriptive scenarios that cover both positive and negative paths with proper setup and teardown. Accordingly, the current change—limited to the pre-commit configuration—does not impact test organization or coverage expectations.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud