|
You are here |
countvajhula.com | ||
| | | | |
tomasvotruba.com
|
|
| | | | | In the previous post, we looked at [Why is First Instant Feedback Crucial to Developers?](/blog/2020/01/13/why-is-first-instant-feedback-crucial-to-developers/). We know why now we look at *how*. How exactly migrate all jobs from Travis to GitHub Actions, **reduce stress from long feedback loops** and live a more healthy life as a programmer. Yes, in code samples :) | |
| | | | |
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. | |
| | | | |
earthly.dev
|
|
| | | | | Learn how to automate the process of developing, testing, building, and deploying Docker containers using GitHub Actions. This tutorial will guide ... | |
| | | | |
initialcommit.com
|
|
| | | In this article, we explore three options for continually deploying content to S3: Git server hooks, GitHub Actions, and Bitbucket Pipelines. | ||