Build CSS with CI about nes.css HOT 10 CLOSED

@BcRikko of course! I did fork and start working on setting up CI this afternoon. You can check out what I’ve got so far on my fork: https://github.com/trezy/NES.css/blob/master/.circleci/config.yml

from nes.css.

I agree 👍
It's too much hassle to resolve conflicting files... 😢

so, I'd like to build CSS(dist files) with CI. 🛠

from nes.css.

Travis CI

Always free for open source projects
https://travis-ci.com/plans

Circle CI

1,000 build minutes per month
https://circleci.com/pricing/

from nes.css.

@BcRikko Have you already started on this? If not, I'd love to help out. I'll fork this afternoon and get it set up on CircleCI if that works for you.

I also have a few suggestions that would make it easier to manage the community that you're very swiftly building.

1. Create a develop branch
   Many large repositories have a develop branch for people to merge their pull requests into. This allows the original repo to accept a PR without merging it directly into master, therefore allowing CI to run without affecting production builds.
2. Set up Commitizen
   With a popular repo like this, there are a lot of different contributors, each with their own style of writing. This is great because it means more features get created faster and more bugs get fixed sooner, but it also makes it really hard to review commits just based on their messages. Commitizen helps out by forcing contributors to use a standard commit message format.
3. Set up semantic-release
semantic-release automates the entire process of version bumping, changelog generation, and publishing to package managers (like npm). It's a great thing to set up with CI because, as they say in their README:

   ...releases are guaranteed to be unromantic and unsentimental.

Again, I don't want to step on your feet so let me know if you want me to chip in on this one. 😉

from nes.css.

I have not started this issue yet.
I'm the first time that I became the owner of a product that many people pay attention. 😨

so, please help me 🙏
and could you give me some advice please? 🙏

from nes.css.

oh, Thanks 🎉🎉🎉

from nes.css.

How about adding the built css to gitignore once this is done? 🙏

from nes.css.

Yes, let CI build css.

from nes.css.

Yup, I'm working on getting semantic-release set up right now. Once that's done I'll make the PR, then we can make separate issues to cover adding release targets (cdnjs, npm, etc). Once that's done, it'll make sense to remove the compiled CSS files from the repo. 😁

from nes.css.

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from nes.css.