fix: correct malformed .gitignore Cargo.lock entry#65
Conversation
'Cargo.lock (shared)' was not a comment (no leading #); git read it as a pattern matching a literal file named 'Cargo.lock (shared)', and it did NOT ignore Cargo.lock (which is correctly committed). Replace with a real comment explaining why Cargo.lock is tracked. Closes #44
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR fixes a malformed ChangesGitignore Configuration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minute Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
The last line of
.gitignorewasCargo.lock (shared)— not a comment (comments need a leading#). Git interpreted it as a pattern matching a file literally namedCargo.lock (shared); it did not ignoreCargo.lock(which is correctly committed for a binary workspace), and the trailing text was misleading.Changes
Cargo.lockis tracked.Closes #44
Summary by CodeRabbit