Explore >> Select a destination
|
You are here 
|
daniel-m.github.io | ||
| | | | |
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. | |
| | | | |
www.harness.io
|
|
| | | | | This blog walks you through the advantages of this feature and how you can configure it for a seamless Continuous Delivery experience. | |
| | | | |
bpohoriletz.github.io
|
|
| | | | | Time: 30-45 min Level: Intermediate Code: Application Revision: May 14, 25 | |
| | | | |
andrewlester.net
|
|
| | | Deploying a SvelteKit application to GitHub Pages. | ||
