How to deal with Cargo.lock
Sorry for the not-so surfer related question, asking because it's kind of "caused" by the pre-commit hooks...
How do you deal with the pre-commit checks (clippy/test) updating Cargo.lock
? This happens to me often when e.g. putting in review feedback.
Should we just keep the updated Cargo.lock
? I'm asking because I was kind of assuming that you might want to keep an older Cargo.lock
since you checked it in in the first place. (A similar issue also happens when editing/rebasing with older commits in an editor that is running rust-analyzer, which is always forcing an update of Cargo.lock
)