Update renovate and prek documentation#122
Conversation
📝 WalkthroughWalkthroughThe pull request migrates the project from the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #122 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 2 2
Lines 7 7
=========================================
Hits 7 7 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
🧹 Nitpick comments (3)
docs/tools/prek.md (2)
5-5: Consider clarifying the migration note for existing users.Since this PR migrates the template from
pre-committoprek, it might be worth explicitly mentioning thatprekis a drop-in, Rust-based reimplementation that reuses the same.pre-commit-config.yaml, so existing hooks keep working. That framing helps readers understand why the config filename still referencespre-commit.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/tools/prek.md` at line 5, The migration note about prek is unclear for existing users; update the text in the prek documentation to state that prek is a drop-in, Rust-based reimplementation that reuses the existing .pre-commit-config.yaml so current pre-commit hooks continue to work, and explicitly explain that this is why the config filename still references pre-commit; mention the terms "prek" and ".pre-commit-config.yaml" in the sentence so readers understand compatibility and the reason for the unchanged filename.
7-7: Optional: minor wording polish.LanguageTool flags two small style nits you may want to address for consistency with the rest of the docs.
✏️ Proposed wording tweaks
-The `prek` related settings are defined in the `.pre-commit-config.yaml` file. +The `prek`-related settings are defined in the `.pre-commit-config.yaml` file.-I used to use [pre-commit](https://pre-commit.com){target} before, but switched to `prek` as it seems to be more actively maintained. +I used to use [pre-commit](https://pre-commit.com){target} before, but switched to `prek` as it seems more actively maintained.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/tools/prek.md` at line 7, The sentence "The `prek` related settings are defined in the `.pre-commit-config.yaml` file." needs minor wording polish: change "`prek` related" to a hyphenated form ("`prek`-related") and simplify the file reference by removing the extra "file" word or trailing period for consistency with other docs; update the sentence containing "The `prek` related settings" and the `.pre-commit-config.yaml` reference accordingly.docs/tools/renovate.md (1)
7-7: Optional: minor wording/casing nits.✏️ Proposed tweaks
-The `renovate` related settings are defined in the `.github/renovate.json5` file. +The `renovate`-related settings are defined in the `.github/renovate.json5` file.The LanguageTool “GitHub” casing hint is a false positive here —
.github/is the correct directory name.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/tools/renovate.md` at line 7, The sentence referencing the renovate settings should keep the literal `.github/renovate.json5` directory name and avoid changing its casing; update the wording if desired but do not alter `.github/renovate.json5` (the string `.github/renovate.json5` and the term `renovate` identify the target text). If you rephrase, make it a concise sentence like "The renovate settings are defined in `.github/renovate.json5`." and ensure the directory name remains exactly `.github/` to avoid the LanguageTool false positive.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@docs/tools/prek.md`:
- Line 5: The migration note about prek is unclear for existing users; update
the text in the prek documentation to state that prek is a drop-in, Rust-based
reimplementation that reuses the existing .pre-commit-config.yaml so current
pre-commit hooks continue to work, and explicitly explain that this is why the
config filename still references pre-commit; mention the terms "prek" and
".pre-commit-config.yaml" in the sentence so readers understand compatibility
and the reason for the unchanged filename.
- Line 7: The sentence "The `prek` related settings are defined in the
`.pre-commit-config.yaml` file." needs minor wording polish: change "`prek`
related" to a hyphenated form ("`prek`-related") and simplify the file reference
by removing the extra "file" word or trailing period for consistency with other
docs; update the sentence containing "The `prek` related settings" and the
`.pre-commit-config.yaml` reference accordingly.
In `@docs/tools/renovate.md`:
- Line 7: The sentence referencing the renovate settings should keep the literal
`.github/renovate.json5` directory name and avoid changing its casing; update
the wording if desired but do not alter `.github/renovate.json5` (the string
`.github/renovate.json5` and the term `renovate` identify the target text). If
you rephrase, make it a concise sentence like "The renovate settings are defined
in `.github/renovate.json5`." and ensure the directory name remains exactly
`.github/` to avoid the LanguageTool false positive.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: d5395df3-4343-4039-a4d7-522795f7e4d3
📒 Files selected for processing (7)
JustfileREADME.mddocs/tools/index.mddocs/tools/pre-commit.mddocs/tools/prek.mddocs/tools/renovate.mdzensical.toml
💤 Files with no reviewable changes (2)
- docs/tools/pre-commit.md
- README.md
There was a problem hiding this comment.
Pull request overview
Updates the documentation/navigation to reflect using Prek for git hooks and adds a new docs page for Renovate dependency updates.
Changes:
- Replace the “Pre-Commit” docs entry with “Prek” and add “Renovate” in the Zensical navigation and tools index.
- Add new documentation pages for
prekandrenovate, and remove the oldpre-commitdocs page. - Update the
Justfilerecipe name frompre-committoprek, and remove the pre-commit.ci badge from the README.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
zensical.toml |
Updates docs navigation to point to tools/prek.md and tools/renovate.md. |
docs/tools/renovate.md |
Adds Renovate documentation and references .github/renovate.json5. |
docs/tools/prek.md |
Adds Prek documentation and usage examples (including just prek). |
docs/tools/pre-commit.md |
Removes obsolete Pre-Commit documentation page. |
docs/tools/index.md |
Updates the tools list to include Prek and Renovate. |
README.md |
Removes the pre-commit.ci status badge. |
Justfile |
Renames the recipe to prek to match the new hook runner. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
✅MegaLinter analysis: Success
See detailed reports in MegaLinter artifacts
|

Summary by CodeRabbit
Documentation
Refactor