If the source code is not linted for every commit and poorly formatted code stays, it turns into a disaster pretty fast since lint-formatting commits usually do not merge automatically.
If we don't care formatting "at all", it's ok.
But if we do care, rebasing on such commits is a painful job.
So how about applying travis-ci?
travis-ci can test and flag go or no-go for each pull request automatically.
Applying only eslint would suffice for now, and we can add some tests later if needed.
https://travis-ci.org/
If the source code is not linted for every commit and poorly formatted code stays, it turns into a disaster pretty fast since lint-formatting commits usually do not merge automatically.
If we don't care formatting "at all", it's ok.
But if we do care, rebasing on such commits is a painful job.
So how about applying travis-ci?
travis-ci can test and flag go or no-go for each pull request automatically.
Applying only eslint would suffice for now, and we can add some tests later if needed.