-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Build CSS with CI #13
Comments
Travis CI
Circle CI
|
@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.
Again, I don't want to step on your feet so let me know if you want me to chip in on this one. 😉 |
I have not started this issue yet. so, please help me 🙏 |
@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 |
oh, Thanks 🎉🎉🎉 |
How about adding the built css to gitignore once this is done? 🙏 |
I agree 👍 so, I'd like to build CSS(dist files) with CI. 🛠 |
Yup, I'm working on getting |
Add `semantic-release` to the repo and the build pipeline. This will handle automatically publishing to npm based on commit messages. #13
The Roll For Guild Node container doesn't include `git`, which is required by semantic-release. #13
Add `commitlint` to enforce proper formatting for all commit messages #13
Since we don't have any tests yet, we want to make sure the build runs successfully on all branches. That way we can at least verify that the build works correctly. closes #13
This removes `semantic-commitlint` from both the local build pipeline and the CI build pipeline. The original value of `semantic-commitlint` was that it would handle linting only the relevant commits, i.e. the commit range under review for a PR. However, the library doesn't seem to respect our altered `commitlint` rules, so we'll be switching to an alternate strategy to handle linting of specific ranges. #13
I've added `circleci-commitlint-step` because it *should* handle linting of the appropriate commitlint ranges via a specialized Docker container for CircleCI with a commit range. #13
🎉 This issue has been resolved in version 1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
cssファイルがコンフリクトしてしまうので、masterにマージしたときにCIでビルドしたい
The text was updated successfully, but these errors were encountered: