add gitignore

[bennyz]

Summary by CodeRabbit

• Chores
  • Added repository configuration to manage build artifacts and temporary files.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

A new .gitignore configuration file is introduced for a Rust/Cargo project, specifying patterns to exclude build artifacts, compiler backups, debug files, and test output from version control.

Changes

Cohort / File(s)	Summary
Project Configuration .gitignore	New file added with ignore patterns for Rust/Cargo projects: excludes debug/, target/, RustFmt backups (**/*.rs.bk), MSVC pdb files, and mutation testing artifacts. Includes commented guidance for JetBrains IDE configuration.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Whiskers twitching with glee,
I've sorted what should and shouldn't be,
Build files hidden, targets ignored with care,
Git's garden now pristine and fair! 🌱✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'add gitignore' is vague and generic, lacking specificity about what the .gitignore file accomplishes or which project type it targets.	Consider a more descriptive title such as 'add .gitignore for Rust/Cargo project' to clearly convey the purpose and context of the change.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.gitignore (1)

16-21: Consider adding common editor/OS-specific patterns.

The JetBrains section follows best practices by referencing the official template. You may want to expand the file to include other common development tool patterns.

Common additions to consider:

 # RustRover
 #  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
 #  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
 #  and can be added to the global gitignore or merged into this file.  For a more nuclear
 #  option (not recommended) you can uncomment the following to ignore the entire idea folder.
 #.idea/
+
+# VS Code
+.vscode/
+
+# Editor backups
+*~
+*.swp
+*.swo
+
+# OS files
+.DS_Store
+Thumbs.db

Whether to include Cargo.lock depends on your project type: libraries typically exclude it, while binaries usually include it for reproducibility.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0df405c and 1d57470.

📒 Files selected for processing (1)

• .gitignore

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)

• GitHub Check: Build (aarch64-unknown-linux-gnu)
• GitHub Check: Build (aarch64-unknown-linux-musl)
• GitHub Check: Build (x86_64-unknown-linux-gnu)
• GitHub Check: Build (aarch64-apple-darwin)
• GitHub Check: Build (x86_64-apple-darwin)
• GitHub Check: Test

🔇 Additional comments (1)

.gitignore (1)

1-14: Core Rust patterns look good.

The .gitignore correctly covers standard Cargo build artifacts, platform-specific debug files, and mutation testing output. The patterns are properly formatted and appropriately commented.

[mangelajo]

Looks good, not sure why the linter now complains on this, although I think some of those linting details have been handled on the OCI PR