Explore >> Select a destination
|
You are here 
|
code.dblock.org | ||
| | | | |
nickcharlton.net
|
|
| | | | | Last year, I started to see a few common workflows that would create more work by those unaware or open yourself up to making annoying mistakes if you did, that I thought could be caught with just a little more automation. | |
| | | | |
wittchen.io
|
|
| | | | | Recently GitHub introduced really interesting feature to their service called Actions. Actions can be used for automating various tasks related to the repositories like CI, CD, testing, deployment and whatnot. The general concept is as follows: We can create so called action, which can be based on a JavaScript project or a Docker container. We can also use existing actions in the Marketplace. Next, we can create workflow in the yml file, where we define our workflow. Workflow can consist of on a job with many steps using different actions. We can also define multiple jobs, where one depends on another. Workflows can be triggered in many ways. E.g. by push, pull request, creating issue, publishing release, scheduled event or external event. | |
| | | | |
aayushsahu.com
|
|
| | | | | ||
| | | | |
blog.foletta.net
|
|
| | | The HTML5 Herald | ||
