Open monty5811 opened 8 years ago
I've never heard of it. I looked it up and it sounds interesting. I'm not opposed to it.
It looks very similar to greenkeeper.io for Node projects. If that's correct, I'd recommend using requires.io, because it would take some of the pain out of the job of keeping your dependencies up-to-date. greenkeeper.io submits a pull request, and if you've got continuous integration (like travis-ci.org) set up with Github, then the continuous integration (build) server runs your test suite, and if they all pass, then the build server merges the pull request into master, and (if you're using semantic-release) creates a new release on Github with a semantic version number, and creates a changelog for that release organized according the commit conventions used by semantic-release.
Should we us requires.io to keep libraries up to date?