Skip to content
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

CLI output is confusing when only file hashes have changed #1184

Open
camjackson opened this issue Feb 16, 2024 · 0 comments · May be fixed by #1185
Open

CLI output is confusing when only file hashes have changed #1184

camjackson opened this issue Feb 16, 2024 · 0 comments · May be fixed by #1185

Comments

@camjackson
Copy link

As described in this discord message, betterer in CI mode can be confusing when the only mismatch is the file hash, and not the issues in a file.

In this situation, betterer will say:

All checks stayed the same

... followed immediately by:

Unexpected changes detected in these tests...

Ideally it would say something like:

All checks stayed the same, however, the file hash has changed for path/to/file.txt. Please re-run betterer locally to update all file hashes in betterer.results.

I'm going to see if I can fix this and open a PR...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant