Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Idea] CI with Travis #12

Open
marverix opened this issue Feb 5, 2019 · 2 comments
Open

[Idea] CI with Travis #12

marverix opened this issue Feb 5, 2019 · 2 comments

Comments

@marverix
Copy link
Contributor

marverix commented Feb 5, 2019

How about integration with Travis? Whenever someone will create PR, Travis would run tests - so you will know if it's safe to merge it or not? :)

@roddeh
Copy link
Owner

roddeh commented Feb 6, 2019

I am not familiar with Travis. Generally I am open to any improvements to tooling so long as they don't create hard dependencies (I am regretting CoffeeScript for example).

@marverix
Copy link
Contributor Author

marverix commented Feb 7, 2019

I'm using CS 1.x in my job (as when I came it was already used). Yes, it has it downsides, but for the time it was ok. I still like it. But if you regret having it in CS how about moving it to ES6, and as bundler using rollup.js + babel plugin (check my repo for example: https://github.com/marverix/rollup-plugin-copier ).

So how about this roadmap:

  1. Move tests to Mocha ([Idea] Move Tests to Mocha + Chai #10).
  2. Move CoffeeScript to ES6.
  3. Run tests if we didn't brake anything.
  4. Add Linter (eslint) ([Idea] Linter #11)
  5. Add Travis ([Idea] CI with Travis #12).
  6. Add husky (https://github.com/typicode/husky).

Ofc I will be glad to help you with above, especially that I'm using above technologies e.g. in repo that I mentioned above.

Br,
Marek

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants