remove radon reports #242
Merged
remove radon reports #242
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Makes sense. Maybe it's better to put all that kind of stuff in a separate repository? |
|
Yeah if you want to keep that stuff in version control I'd definitely just toss it into a "whipper-metrics" repository or something along those lines. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I don't believe code diagnostics beyond our coverage reports (which I'm not fully convinced of the utility of adding either, but we inherited that habit) is useful. They're quickly out of date with every commit and are more of a developer's tool than an important feature of whipper that every copy of the source code needs to have alongside. We don't (nor should we!) store the output of flake8 or sloccount either, etc.