Skip to content
This repository has been archived by the owner on Apr 9, 2019. It is now read-only.

The need for a CI #3

Open
Richienb opened this issue Dec 24, 2018 · 4 comments
Open

The need for a CI #3

Richienb opened this issue Dec 24, 2018 · 4 comments

Comments

@Richienb
Copy link
Contributor

This repository should be taking advantage of a CI like Travis CI. Such a CI would be able to automatically release code to npm, compile scss and add prefixes.

My suggestion here is to integrate this project with Travis Ci, give Travis a gituhb token and then configuring it to compile scss, add prefixes, minify it then release it to npm. Therefore, people can use services like jsdelivr to use your code instead of having to download the boilerplate code every single time.

@martonlederer
Copy link
Owner

I might make it however I don't have much time for it right now. I'll leave this issue opened, until I make it

@Richienb
Copy link
Contributor Author

I, however, do have a bit of time on my hands. Therefore I suggest you should connect it to travis-ci.com, set a repository token and I'll see what I can do.

@martonlederer
Copy link
Owner

martonlederer commented Dec 25, 2018

Well okay, I'll do it tomorrow. Thank you

@Richienb
Copy link
Contributor Author

Sure.

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

No branches or pull requests

2 participants