-
Notifications
You must be signed in to change notification settings - Fork 92
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
Add compiled file to a dist folder #27
Comments
Actually, there is. The reason why
|
I think you misunderstood the point. What I want to explain is that one
|
Oh, sorry I missed your point. Anyway, now that makes sense. |
@rultor release, tag is |
@yegor256 ah, the branch was __rultor .. Should've chekout to master before commit. |
I don't have access to bower/node or any of those fancy command line tools on the server that I have to use (shared host). I'd really like just a CSS file I can download and drop in. |
@vote539 of course, it's here: http://yegor256.github.io/tacit/tacit.min.css |
@yegor256, we can close this issue. With regards to the user request of
We're already doing this each release, example: We could follow, for example, Bootstrap's aproach and also place the css results of compilation in a "master"-like branch: But this violates the idea of the protected master branch discussed in some of your blog posts. And I'd add it would look ugly compared to what we have now, separating development repo and release of artifacts. |
@ylecuyer @filfreire that's right, closing |
The job is not in WBS, won't close the order |
When using tacit with bower it would be usefull to have
tacit.min.css
andtacit.css
in a dist folderThe text was updated successfully, but these errors were encountered: