ignore gitguardian swift false positives

[transphorm]

Summary by CodeRabbit

• Chores
  • Updated configuration file to expand ignore rules for development frameworks and interface files, enhancing security scanning precision.

[coderabbitai]

Walkthrough

GitGuardian ignore patterns expanded in .gitguardian.yml to exclude nested iOS framework directories (*.xcframework) and Swift interface files (*.swiftinterface) from both paths-ignore and secret.ignored_paths sections.

Changes

Cohort / File(s)	Summary
GitGuardian Configuration \.gitguardian.yml	Added ignore patterns for *.xcframework nested contents and *.swiftinterface files in both paths-ignore and secret.ignored_paths sections

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Simple, homogeneous configuration changes across two related sections
• No behavioral or logic modifications; purely additive ignore patterns

Poem

🔐 Swift frameworks fade from sight,
Interface files tucked out of light,
GitGuardian keeps secrets tight,
iOS builds—now clean and bright! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "ignore gitguardian swift false positives" directly describes the main objective of the changeset, which is to expand ignore rules in .gitguardian.yml to prevent false alerts when scanning Swift and iOS framework files. The title is concise, clear, and accurately communicates the core intent without unnecessary details like specific file patterns or emoji. A team member reviewing the commit history would immediately understand that this PR addresses GitGuardian configuration to suppress Swift-related false positives, making the purpose immediately evident.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch justin/ignore-gitguardian-swift-false-positives

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4f00dcd and a53382e.

📒 Files selected for processing (1)

• .gitguardian.yml (2 hunks)

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

• GitHub Check: type-check

🔇 Additional comments (2)

.gitguardian.yml (2)

41-42: Pattern additions look good for iOS frameworks and Swift interface files.

The patterns correctly complement existing rules: **/*.xcframework/** explicitly matches nested directory contents, while **/*.swiftinterface covers Swift interface files. Syntax and placement are consistent with the rest of the configuration.

---

61-62: Verify these patterns resolve the reported false positives.

The same patterns are properly mirrored in the secret.ignored_paths section. Ensure these additions suppress the GitGuardian false positives you're targeting without being overly broad.

---

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.}