Difference between revisions of "GitHub Actions"
Jump to navigation
Jump to search
↑ https://techcrunch.com/2018/10/16/github-launches-actions-its-workflow-automation-tool/
| Line 1: | Line 1: | ||
[[wikipedia:Github Actions]] (2018)<ref>https://techcrunch.com/2018/10/16/github-launches-actions-its-workflow-automation-tool/</ref> allows building [[continuous integration]] and [[continuous deployment]] pipelines for testing, releasing and deploying software without the use of third-party websites/platforms. | [[wikipedia:Github Actions]] (2018)<ref>https://techcrunch.com/2018/10/16/github-launches-actions-its-workflow-automation-tool/</ref> allows building [[continuous integration]] and [[continuous deployment]] pipelines for testing, releasing and deploying software without the use of third-party websites/platforms. | ||
| + | |||
| + | [[.github/workflows/]] | ||
== See also == | == See also == | ||
Revision as of 11:28, 5 May 2021
wikipedia:Github Actions (2018)[1] allows building continuous integration and continuous deployment pipelines for testing, releasing and deploying software without the use of third-party websites/platforms.
.github/workflows/
See also
- GitHub, GitHub Actions, GitHub Actions Runner, Events, CodeQL, GitHub Desktop, GitHub organization, base permissions, GitHub Copilot,
.gitignore, GitHub Codespaces, GitHub Marketplace, GitHub Apps, GitHub Enterprise Server, GitHub CLI (gh), Dependabot, GitHub security,.github/, GitHub code scanning, GitHub Pages, GitHub Packages, GitHub Advanced Security, GitHub Mobile, GitHub Importer, GitHub versions, SSH keys - Continuous integration (Continuous delivery): GitLab CI, TeamCity, Travis CI, Jenkins, CloudBees, AWS CodePipelines, Azure Pipelines, XebiaLabs, Codefresh, GitHub, Pipeline, CircleCI, JFrog Pipelines, Concourse CI, Dagger, Bitbucket Pipelines, Buildkite, Google Cloud Build
Advertising:
