Add navigation links to compliance docs#1275
Conversation
All control IDs (C-001..C-046) in compliance_track.rst now link to their anchored entries in control_register.rst. File paths in the Reference column of control_register.rst link to their source on GitHub. Doc paths use :doc: cross-references. SECURITY.md and OSCAL artefact references throughout compliance_track.rst and security.rst link directly to the relevant GitHub pages. https://claude.ai/code/session_01DhTruTejopMJeFWfBKUtud
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
WalkthroughThree RST documentation files are updated with no logic changes. ChangesCompliance Documentation Cross-Reference Update
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 |
All control IDs (C-001..C-046) in compliance_track.rst now link to their
anchored entries in control_register.rst. File paths in the Reference
column of control_register.rst link to their source on GitHub. Doc
paths use :doc: cross-references. SECURITY.md and OSCAL artefact
references throughout compliance_track.rst and security.rst link
directly to the relevant GitHub pages.
https://claude.ai/code/session_01DhTruTejopMJeFWfBKUtud
Summary by CodeRabbit