Github Actions

Be lazy, automate: GitHub Actions for static blogging /me: Pablo Iranzo Gómez ( https://iranzo.io ) What is a blog? A place to share knowledge, interests, tips, etc. Usually features: images comments from visitors, related articles, etc. What are the costs for a blog? Web costs money: Hosting Domain Maintenance etc. What is static blogging? Generate a static webpage Think of it as rendering templates into HTML Has no requirements on the web server, any simple Webserver is enough: Look ma!...

During last year I’ve worked with the https://github.com/openshift-kni/baremetal-deploy/ repository after being working in the KNI Community team that was in charge of <KubeVirt.io> and <Metal3.io> where some of the below things were applied. One of the goals we had was to streamline the upstream <-> downstream process to keep changes done in the right way: get changes upstream and copy over downstream with minimal changes. We ended up using AsciiDoctor for building the documentation in the same way it’s done downstream so it’s just a matter of copying over the modules....

When I started with blog-o-matic I had to involve external ‘Travis-CI’, generating a token on GitHub, setting environment variables on Travis, etc GitHub started enabling actions which allows to automate workflows in a similar way than Travis or other external providers allowed, but with one extra feature: configuration is defined inside .github/ folder of your repository, which makes incredibly easy to copy the setup for one tool to another (except of optional required tokens that are configured per repo)....