-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Regal documentation #181
Conversation
WalkthroughThe documentation for Regal, the language server for Rego (Open Policy Agent's language), has been updated to provide more precise and consistent information. The changes focus on clarifying the tool's description, specifying the exact configuration file location, and standardizing terminology related to configuration settings. Changes
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/tools/regal.md
(2 hunks)
🔇 Additional comments (1)
docs/tools/regal.md (1)
13-13
: LGTM! Clear and informative description.
The updated description provides better context by explicitly mentioning Rego's relationship with OPA and including appropriate links.
@coderabbitai fix this
|
Tip For best results, initiate chat on the files or code changes. @alexcoderabbitai: It looks like the checkout step is failing because Git can’t fetch the
Let me know if this helps resolve the issue. |
Corrected the broken configuration link, and made a few small edits to the copy.
Corrected the broken configuration link, and made a few small edits to the copy.