feat: add more file type

[aftersnow]

Summary by CodeRabbit

• New Features
  • Expanded recognition of configuration, model, code, and documentation file types, including additional programming languages, config formats, image, and video formats.
• Documentation
  • Updated file type support to cover a broader range of formats for easier file identification.

[coderabbitai]

Walkthrough

The update expands the recognized file pattern lists in the pkg/modelfile/constants.go file. New extensions were added for configuration, model, code, and documentation files, covering a broader range of file types and programming languages. No logic or function signatures were changed; only the pattern lists were extended.

Changes

File(s)	Summary
pkg/modelfile/constants.go	Expanded file pattern lists for config, model, code, and documentation files with new extensions; no logic changes.

Poem

The file list grows, a pattern parade,
From configs to code, new types are displayed.
Docs and models join the dance,
With every extension, more files have a chance.
A rabbit’s delight, this pattern bouquet—
Now every file can come out and play! 🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (1.64.8)

Error: you are using a configuration file for golangci-lint v2 with golangci-lint v1: please use golangci-lint v2
Failed executing command with error: you are using a configuration file for golangci-lint v2 with golangci-lint v1: please use golangci-lint v2

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4e82fe0 and 565a02c.

📒 Files selected for processing (1)

• pkg/modelfile/constants.go (4 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• pkg/modelfile/constants.go

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Test
• GitHub Check: Analyze (go)
• GitHub Check: Lint

✨ Finishing Touches

• 📝 Generate Docstrings

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (4)

pkg/modelfile/constants.go (4)

27-41: Broadening config file support looks good. The added generic config and XML-related extensions (*.cfg, *.conf, *.properties, *.props, *.prop, *.xml, *.xsd, *.rng) enhance flexibility. Consider alphabetically ordering this slice or grouping by type (e.g., JSON, YAML, XML, generic) to improve maintainability.

---

67-77: Good coverage of additional model formats. The new extensions (*.ot, *.engine, *.trt, *.onnx, *.gguf, *.msgpack, *.model, *.pkl, *.pickle, *.ckpt, *.checkpoint) encompass major frameworks. For future ease of navigation, consider sorting them alphabetically.

---

82-132: Extensive expansion of code file patterns. The inclusion of many new source, header, and library file extensions is comprehensive. To boost readability, you may break this large slice into sub-categories (e.g., scripts, sources, headers, binaries) or sort entries alphabetically. Also, update the slice comment to reflect that it now covers more than “script and notebook files.”

---

145-171: Enhanced documentation asset support. Adding logs, modern image formats (*.webp, *.heic, *.heif, *.hevc, *.svg) and video formats covers common use cases. For consistency, group and alphabetize entries within each media category (documentation, images, videos).

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6b5f9c9 and 4e82fe0.

📒 Files selected for processing (1)

• pkg/modelfile/constants.go (4 hunks)

🔇 Additional comments (1)

pkg/modelfile/constants.go (1)

43-48: Review tokenizer and variant patterns. The pattern *tokenizer.model* alongside config.json.* covers diverse filenames but may be overly permissive—verify it matches only the intended tokenizer files (e.g., my.tokenizer.model) and doesn’t catch unintended files.

[chlins]

lgtm