-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
DevOps (CircleCI): build step
to publish latest version on Github Pages
#165
Comments
There is none... I want to automate the process (as well as the one to generate the font files) for a long time but never took the time to do it... For now, |
Ouh! I see...
Once this is done, build CI cycle. If you agree that, I could work on it. |
Yes sure, would be great ! |
@rjlopezdev are u still interested in contributing? Because an automated build process including the font generation would be amazing. |
Sure! Please, can you explain me the build process in order to I can reply it & automate It? @amacado 🙏 |
I'm working on a document explaining the build process. Update here as soon it's ready |
Awesome! Eager to read it! |
I just published the first version of the documentation in my fork. Feel free to take a look at it and enhance it. I also upgraded to gulp v4 in this pull request, since gulp 3 is not compatible with current node version. I think the main challenge for build automation is the icomoon.app (maybe there is an api?) and we would need to refactor the 'alias'-idea in the stylesheets. |
I'm thinking of integrating the |
Since v2.8.0 we are publishing the devicon.dev from the master branch ( |
I've noticed Devicon Web is not updated with the latest icons.
I could design a simple CI cycle to atomate this proccess:
Steps
gh-pages
branchTriggers
master
branchIf you are interested, I would need the scripts you use to publish on
gh-pages
🙏The text was updated successfully, but these errors were encountered: