2 ms·
After glancing over the README here are a few of the other things I take a look at. The "contributors" tab on GitHub helps get an idea for the health of the pr
by simonw 7y ago
After glancing over the README here are a few of the other things I take a look at.
The "contributors" tab on GitHub helps get an idea for the health of the project: how long has it been actively maintained? Who did most of the work? https://github.com/dgraph-io/dgraph/graphs/contributors https://github.com/dgraph-io/dgraph/graphs/contributors
For software libraries, I like looking at the brand new "used by" tab - https://github.com/huge-success/sanic/network/dependents https://github.com/huge-success/sanic/network/dependents - in addition to indicating project health it's also a great source of examples to look at later when I'm trying to figure out how to do advanced things with the library.
I love reading through the CI configuration - .travis.yml or .circleci/config.yml - because at the very least it shows what it takes to run the test suite, and often I'll pick up some fun new CI and automation tricks.
I use GitHub code search extensively: sometimes for searching within the project, but I'll also search the whole of GitHub for examples of people doing something I want to do with the library: https://github.com/search?q=sanic+cookies&type=Code https://github.com/search?q=sanic+cookies&type=Code
- TehShrike 7y agoGood tip about Github's code search, I always forget it's a thing and don't use it nearly as much as I should