How do tell LlamaPReview to ignore reviewing generated files

[Rohithgilla12]

Thanks for this amazing app.
We have generated files, how do we tell the bot to not look at them but only focus on the main files?

Can we also give any custom instructions?

Thanks

[JetXu-LLM]

Hi @Rohithgilla12, thanks for your interest in LlamaPReview!

For ignoring generated files in PR reviews, there are a few options:

1. Built-in File Skip Rules
   LlamaPReview (powered by llama-github) already has built-in logic to skip certain types of files like .ipynb, .dll, .svg, etc. These rules are maintained in the core llama-github library.

2. Custom Skip Rules
   Could you please share more details about:

   • What types of generated files you want to skip?
   • Are these files following any specific naming patterns or located in particular directories?

This information would help us:

• Add appropriate skip rules to llama-github if it's a common use case
• Provide you with specific guidance for your repository's needs

As for custom instructions - yes, we're working on adding more customization options. What specific instructions would you like to give to the bot? This feedback would be valuable for our roadmap planning.

Looking forward to your response so we can better assist you! 🚀

[Rohithgilla12]

Thank you so much, @JetXu-LLM ! 🚀

The skip rules often follow specific naming patterns or conventions across different programming languages. Here are some detailed insights:

Language-Specific Generated File Patterns

Dart/Flutter

• *.g.dart (generated code for JSON serialization)
• *.freezed.dart (files generated by the freezed package for data classes)
• Additional generated files from build tools like build_runner

TypeScript/JavaScript

• Files specified in .eslintignore
• Files in .prettierignore
• Entries in .gitignore

Python

• .ipynb_checkpoints
• Generated .pyc files
• Autogenerated code in .tox
• Virtual environment directories (venv)

Go

• .pb.go (Protocol Buffers generated files)
• *_test.go
• Files in vendor/ directory

C++/C

• .o files
• .so files
• .a files
• Other build artifacts

Implementation Suggestions

1. Language-Specific Lint/Config Files

   • Leverage language-specific configuration files
   • Examples:
     • Dart: Use analysis_options.yaml
     • TypeScript: Utilize .eslintignore or .prettierignore

2. Custom Rules via Regex

   • Allow users to define custom regex patterns
   • Examples:

     .*\.g\.dart
     .*\.freezed\.dart
     .*\.min\.js
     

3. Automatic Detection

   • Create a curated list of common generated file patterns
   • Automatically recognize files for popular frameworks

Customization Wishlist

1. Define project-specific skip rules (e.g., .llamaignore)
2. Integrate with existing linting or configuration files

These suggestions aim to make file skipping more intelligent, language-aware, and customizable. The goal is to reduce noise in code reviews and help reviewers focus on meaningful changes.

Would these approaches help address your generated file skipping needs? I'm happy to provide more specific examples or discuss further! 🚀

[JetXu-LLM]

Thank you @Rohithgilla12 for your detailed suggestions and comprehensive patterns list! 🙏

I'm happy to share that we've implemented these improvements in our latest update:

1. Enhanced file filtering system that covers all the common patterns you mentioned
2. Added an intelligent pre-screening mechanism to optimize review resource allocation

You should notice these improvements in future PR reviews. The system now better handles generated files and provides more focused reviews on meaningful changes.

Your input has been invaluable in making LlamaPReview more efficient. Please feel free to share any additional suggestions or feedback!