-
Notifications
You must be signed in to change notification settings - Fork 0
Stop committing Cargo.lock #8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
e4f12e2
14e3689
f134c07
2de029f
1325019
eea7203
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -20,3 +20,9 @@ proptest-regressions | |
| wheelhouse | ||
| target-bisector* | ||
| /nvidia | ||
|
|
||
| # Cargo.lock is not committed in this fork: the workspace consumes the | ||
| # AdaWorldAPI/ndarray fork by git branch, and a committed lock pins a stale | ||
| # revision of it (measured: the lock held ndarray e55af0e3 while the branch | ||
| # was at f43338fb, so builds silently used a two-merge-old dependency). | ||
| Cargo.lock | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
On any persistent developer checkout, the first Cargo command recreates this ignored Useful? React with 👍 / 👎. |
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The recorded commit IDs and “two-merge-old” measurement describe a one-time repository state rather than the current contract; as soon as the branch advances, this explanation becomes stale while remaining in the configuration. State the durable reason for the ignore rule without narrating the prior lock contents.
AGENTS.md reference: AGENTS.md:L272-L272
Useful? React with 👍 / 👎.