Update excluded paths in .fortlsrc#1248
Conversation
Removed excluded paths from .fortlsrc configuration.
|
CodeAnt AI is reviewing your PR. Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📝 WalkthroughWalkthroughThe PR removes FortLS exclusions for the misc/ directory and three hardcoded IC pre-processor include files, enabling those files to participate in FortLS analysis. Additionally, the Claude code review GitHub Actions workflow is updated with full output display, Bash-only tool restrictions, and an expanded prompt message. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 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 |
|
CodeAnt AI finished reviewing your PR. |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pull request overview
Updates the Fortran Language Server configuration (.fortlsrc) by simplifying the excluded-paths list, keeping the project’s fortls indexing focused on core source areas.
Changes:
- Removed
misc/fromexcl_paths. - Removed several
src/pre_process/include/*HardcodedIC.fppentries fromexcl_paths.
Updated prompt format for code review action and added option to show full output.
Added claude_args to specify allowed tools for the code review.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/claude-code-review.yml:
- Line 31: The workflow contains an unsupported parameter show_full_output: true
for the claude-code-action@v1 step; remove the show_full_output key (and its
value) from the claude-code-action@v1 configuration so only supported inputs
remain, ensuring the action uses only recognized parameters for
claude-code-action@v1.
- Line 33: The claude_args entry uses the wrong flag and an overly permissive
spec; change the value to use camelCase "--allowedTools" instead of
"--allowed-tools" and replace the broad "Bash" allowance with a tightly scoped
pattern following the Claude CLI syntax (for example restrict to specific
commands/paths or explicit tool names rather than permitting all Bash commands);
update the claude_args setting (symbol: claude_args) so it contains the
corrected "--allowedTools" flag and a scoped tool pattern instead of the plain
"Bash".
Updated Claude Code Review action parameters and removed deprecated settings.
Added new exclusion paths to .fortlsrc configuration.
User description
Removed excluded paths from .fortlsrc configuration.
Description
Summarize your changes and the motivation behind them.
Fixes #(issue)
Type of change
Testing
How did you test your changes?
Checklist
See the developer guide for full coding standards.
GPU changes (expand if you modified
src/simulation/)CodeAnt-AI Description
Include previously excluded files in Fortran language server indexing
What Changed
Impact
✅ Language server indexes pre_process include files✅ Diagnostics available for previously excluded files✅ Code navigation available in misc/ and the restored include files💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.
Summary by CodeRabbit