fix: revert the behavior checking lockfile's VCS status #15341
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR try to resolve?
Fixes #15339
Lockfile might be gitignore'd,
So it never shows up in
git status
.However,
cargo packag
vcs checks actually performsgit status --untracked --ignored
.It is a bit confusing that lockfile is ignored but still counts as dirty from the report of
cargo package
.There are some more nuances:
We check lockfile's VCS status if the lockfile is ouside the current package root. That means a non-workspace Cargo package will not have this VCS check. I don't think it is good that we have diverged behaviors Hence this revert.
We can always re-evaluate later,
as we've reserved rooms for doing more dirty checks.
#14967 (comment)
How should we test and review this PR?
See if the revert is what we want now.
Or we should do a more thorough check for both workspace and non-workspace cases.
Additional information
This is a revert of f0907fc from #15276