Closed martinheidegger closed 8 years ago
could you be a bit more specific about this one @martinheidegger ?
The chapters should have a travis-script up & running that validates the state of the repository. (Reducing user errors).
Right now nodeschool-admin init
creates a .travis.yml
that will lint the repository every time a push happens. However, after init is finished travis is not being setup to actually setup to trigger when something in the repository changes.
There are several options how to deal with it.
.yml
on('push', checkIfContainsTravisYml(enableTravis))
in a own server like "github-teams" or through nodeschoolbotI would go for the 4. solution, its easiest and it also promotes use of CI services, which is awesome I would say(we need more of that in the js community)
I am okay with 4
Agreed on 4.
Ok, now how can we check that their travis test passed ?
@dinodsaurus We don't need to check that. The travis setup would be solely for the convenience of the chapter maintainer (to make less mistakes)
Right now running
init
and creating achapter.json
ends with the repo being pushed in a clean state. Buttravis
is not yet set up to actually lint the chapter. It would be incredibly awesome if that could work automatically as well but if not: at least a good message for the user on how to do that would be good.