Ensure recent markdown files pass pre-commit verifications#103
Conversation
|
Caution Review failedThe pull request is closed. 📝 WalkthroughWalkthroughDocumentation and CI configuration updates: Copilot instructions expanded with setup, docs, project-management, and CI/CD notes; README and contribution docs receive minor formatting/text fixes; CI workflow pull_request path filters removed so PRs trigger the workflow regardless of modified paths. Changes
Sequence Diagram(s)(omitted — changes are documentation/configuration-only and do not introduce new multi-component control flow requiring a sequence diagram.) Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In @.github/copilot-instructions.md:
- Around line 140-145: The markdown ordered list items ("Add/update tests as
needed" and "Run QA checks: `hatch run qa`") run together in some renderers;
update the list in .github/copilot-instructions.md so there is explicit
separation — either add a period at the end of "Add/update tests as needed." or
insert a blank line between that item and "Run QA checks: `hatch run qa`" to
ensure they render as distinct list entries.
f762b2e to
9e47194
Compare
|



Summary by CodeRabbit
Documentation
Style
Chores