Here's a cute lint feature I haven't seen before: an estimate of how long an issue would take to fix!
Link: https://codeclimate.com/github/Wilfred/metawiki/issues?category=duplication&engine_name%5B%5D=structure&engine_name%5B%5D=duplication
(It's a really small project, so 2 hours seems pessimistic.)
Related Posts
It's odd that games often show the hours played, but I've not seen this in other apps.
"You've spent 20 hours talking to this person." Would this be a usage deterrent? If so, why do many games offer it by default?
I've dabbled with 'conventional commits' for a personal project but I found they slowed me down.
It's not always easy to categorise a commit as a fix, a chore etc. Sometimes refactorings also fix bugs.
Do you use them? I can imagine a large, mature project benefitting more.
Today I learnt that `cargo fix` won't fix code with compiler errors by default, but you can override this!
$ cargo fix --broken-code --allow-dirty && cargo clippy --fix --allow-dirty
This incantation does exactly what I wanted :)