|
You are here |
www.morling.dev | ||
| | | | |
davquar.it
|
|
| | | | | A GitHub Action is the automatic execution of a job, after a specified trigger on a GitHub repository. For example, let's say that we want to run a linter on each new commit, we can create a GitHub action to do it. In this post we'll see a workflow to automatically deploy a Hugo site on GitHub Pages. | |
| | | | |
bluegenes.github.io
|
|
| | | | | I need to edit some documentation for our workflow projects dammit and elvers. These docs are set up in mkdocs, which I love for it's simplicity: I can write all my documentation in markdown, and mkdocs will take care of formatting and building html for web display. Thanks to Charles Reid for getting the lab on mkdocs a few years ago and for building us a custom theme back in 2018! | |
| | | | |
msfjarvis.dev
|
|
| | | | | GitHub Actions paired with GitHub Pages provides an excellent CD platform for a status page. Here's how I used it to create mine. | |
| | | | |
no-kill-switch.ghost.io
|
|
| | | Together with my two friends: Tomek Onyszko & Wojtek Ptak, we've created a small community for Senior Technical Leaders (CTOs, VPs of Eng, Directors of Eng, Architects, ...). What is this about? Meeting interesting people (who share your professional concerns & challenges), learning from each other, both inspiring & being inspired. Some say, "it | ||