Setup CI for testing changes
nschonni opened this issue · comments
Was thinking that Travis could probably be setup to clone down the nodejs/node repo, and any other nodejs repos that are using this to see if changes to the config cause new issues.
Probably OK to just do the main node repo. New rules will only go out when we publish new versions. So other projects can fix up their markdown when they upgrade (which is what we do when we upgrade ESLint and an existing rule becomes more strict, for example).
OK, I had tried to add the node master branch as an NPM dev dependency, but that didn't work.
I'll give a basic Travis a try, if you don't get to it first.