Explore >> Select a destination
|
You are here 
|
ekhabarov.com | ||
| | | | |
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.schakko.de
|
|
| | | | | How to configure Artifactory and GitHub Actions to download dependencies from a private Maven repository inside the Artifactory server. | |
| | | | |
janik6n.net
|
|
| | | | | Build and publish auditable container images with SBOM and SLSA attestation to Azure Container Registry using GitHub Actions | |
| | | | |
lea.codes
|
|
| | | Sprinkle your JavaScript codebase with type annotations in JSDoc, run checks against it and auto-generate documentation. | ||
