-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Move to a CI-powered release process #898
Comments
We are actually already doing this for NPM releases. All PRs into master (with a new version in I'd like to move everything to Travis to give us better control over the process, and e.g. allow us to write the website in something other than Liquid. |
My bad 😓 For some reason I just completely missed this snippet of code... |
Closed with #77 |
Not sure how #77 resolved this issue, but I'm fine closing this as it is more or less resolved with https://github.com/simple-icons/simple-icons-website |
Although it is nice to be able to simply let GitHub worry about building our website, it does limit our choice of build tools significantly. Jekyll - the only static page generator GH supports - puts rather strict restrictions on data structure (this is also why the
_data
folder is named as it is) and Liquid, the templating language, is rather underwhelming.I would prefer moving to a build process that is powered by our CI (currently Travis). This would allow us to build using whatever build tool we want (even a custom one), and allow us far greater freedom over how the project is structured.
We could additionally perform automatic git tagged releases, which would give us a formal changelog (#747).
This is all a bit abstract for now, as this issue is mostly created in order to allow discussion on the topic, but it is a future plan for the project (along with #485)
The text was updated successfully, but these errors were encountered: