{"id":39696,"date":"2020-07-16T06:00:28","date_gmt":"2020-07-16T13:00:28","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/premier-developer\/?p=39696"},"modified":"2020-07-16T13:51:40","modified_gmt":"2020-07-16T20:51:40","slug":"github-actions-overview","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/premier-developer\/github-actions-overview\/","title":{"rendered":"GitHub Actions Overview"},"content":{"rendered":"

In this post, App Dev Managers Bernard Apolinario<\/a>, Sujith Nair<\/a>, and Latha Natarajan<\/a> give a thorough overview of GitHub Actions.<\/p>\n

\n

GitHub Actions enables you to create custom workflows directly in your GitHub repository. You can discover, create, and share actions to perform any job you’d like, including CI\/CD, and combine actions in a completely customized workflow. You can create continuous integration (CI) workflows that build, and test projects written in different programming languages.<\/p>\n

GitHub Actions for JavaScript and TypeScript<\/a><\/p>\n

GitHub Actions for Python<\/a><\/p>\n

GitHub Actions for Java<\/a><\/p>\n

GitHub Actions for Docker<\/a><\/p>\n

Workflows run in Linux, macOS, Windows, and containers on GitHub-hosted machines, called ‘runners’. Alternatively, you can also host your own runners to run workflows on machines you own or manage. For more information see, “About self-hosted runners<\/a>.”<\/p>\n

Workflows<\/h2>\n

A workflow is a configurable automated process made up of one or more jobs. You can setup workflows in your repository to build, test, package, release, or deploy any project on GitHub. Workflows are stored in the .github\/workflows<\/strong> directory in the root of your repository. There is a requirement to have at least one job in a workflow. A job contains a set of steps that perform tasks (Commands or Actions)<\/p>\n

Workflows can be configured to start when:<\/p>\n