he/him 
Code coverage, build status, downloads stats and other related info are useless and noisy.
Show this thread
I don't think I've ever seen a badge in a GitHub README that was actually useful.
-
-
-
Anecdote: I used to love "collecting" badges for my projects' READMEs for no actual reason. Also loved adding top level dot files which I now avoid like the plague.
Show this thread
End of conversation
New conversation -
-
-
Build status is useful surely? Are you referring to badges when reading a README as a user or a creator?
-
Both. As a user it doesn't matter. As a maintainer, build failures should never land in master. And when they do, you get a build failure email. I never ever checked the README for the build status. GitHub aggressively caches images too so it's never accurate.
End of conversation
New conversation -
-
-
I've read an academic paper that indicated they do serve to improve whatever metric they indicate. Test badges lead to tests improving etc.
-
I guess it's a good way to publicly shame yourself, but there's probably much more effective methods.
- 1 more reply
New conversation -
-
-
I don’t mind the npm badge with published version. Saves clicking into the package file.
-
Npm size is also handy
- 1 more reply
New conversation -
-
-
Minified and gzip sizes are very important metrics and should be displayed on more repos. I agree though that most other common badges are useless.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
gzip size and install size are useful. As well as david-dm and snyk badges
-
interesting, when I tried to remove the SauceLabs build status (because it's not useful to users) I was actually notified by email that including a link to the test results on the README is a requirement of free use of the product for open source, so I put it back.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.