Don't warn about ignored files in cargo-fix

[alexcrichton]

They're not being tracked, so no worries if we stomp over them!

[rust-highfive]

r? @matklad

(rust_highfive has picked a reviewer for you, use r? to override)

[bors]

☔ The latest upstream changes (presumably #5762) made this pull request unmergeable. Please resolve the merge conflicts.

[birkenfeld]

Hmm, does this now also ignore untracked .rs source files? That would probably be against the spirit of the warning...

[dwijnand]

Fixes #5771

[killercup]

I agree with @birkenfeld. IIRC, our idea was to warn people when cargo-fix would change files that were not under version control. So, I can see the reason why we should not concern ourselves with files that are explicitly ignored (in .gitignore), but untracked files (e.g. newly created ones), we should still warn about. (Assuming I understand the git lingo correctly, I'm looking at git2 docs and the git book.)

[alexcrichton]

r? @killercup

@bors: delegate=killercup

Updated to include untracked files!

[bors]

✌️ @killercup can now approve this pull request

[killercup]

Thanks, Alex! LGTM

@bors r+

[bors]

📌 Commit 6cdee67 has been approved by killercup

[bors]

⌛ Testing commit 6cdee67 with merge c744090...

[bors]

☀️ Test successful - status-appveyor, status-travis
Approved by: killercup
Pushing c744090 to master...

[Eh2406]

Is this going to be affected by https://github.com/alexcrichton/git2-rs/issues/334, if not is this an alternative workaround for #5733?

[alexcrichton]

@Eh2406 I believe this is using a different API so it shouldn't need that fix

[durka]

Do we know when this will be out in nightly? Latest nightly's cargo is a week old.