Episode 28
028: GitHub Actions
We discuss best practices to setup GitHub Actions to make sure everyone has the same source of truth for checking your Elm code and deploying to production.
April 12, 20211h 7m
Audio is streamed directly from the publisher (cdn.simplecast.com) as published in their RSS feed. Play Podcasts does not host this file. Rights-holders can request removal through the copyright & takedown page.
Show Notes
- Continuous Integration (CI)
- CD (Continuous Delivery, Continuous Deployment)
- Mob programming
elm-program-testepisode- Cypress testing framework
- GH actions
onevents (schedule,workflow_dispatch,pull_request, etc.) elm-review new-package- npm-run-all
- Can run
npm-run-all test:*, but don't know the order it will run in - git hooks
- Dependabot
- Dillon's blog post about using dependabot for Elm dependencies
- Send a tweet with a GH action
- Dillon's GH profile (and the GH action workflow for it)
- GH Action to include blog posts in profile feed
- GitHub's Octokit API
- Core GitHub Actions JavaScript packages
- JavaScript GitHub Actions starter template
- Unix toolchain philosophy
- elm-tooling-action
- Simon Lydell's example GitHub Actions workflow
- GitHub Actions cache api
- Brian Douglas' dev.to blog post series
- Edward Thomson's GitHub Actions advent calendar