Automate your software workflow with GitHub Actions. Learn about the main features of this developer productivity and CI/CD suite of tools.
- [Instructor] Programmers use a number of tools to help them take care of common tasks. But over time, this has caused something called developer fatigue, because the number and variety of tools change all the time. Hey there, I'm Ray Villalobos, and in this course, I want to show you a solution that could help offload some of the tooling to GitHub. Now this is called GitHub Actions, so let's take a look at how they work. You create actions in your repositories by creating one or more text files. These are called workflows. Now, workflows can handle common build tasks, like continuous delivery and continuous integration. That means that you can use an action to compress images, test your code and push the site to your hosting platform when the master branch changes. You can also have tasks that run on a specific timeframe, or that control what happens when somebody interacts with the GitHub repository itself. So, when someone makes a comment on a pull request, it can send you a note or you can run an action when somebody stars your project. Actions can run in a variety of platforms, including Linux, macOS or Windows, and these will run on virtual machines or containers. Now that means you can test your code in different environments. You can even run matrix workflows so you can test in multiple platforms simultaneously. Now, Actions can run on any language, including Node.js, Rust, Python, PHP and lots more. Every action creates detail logs which can be used to troubleshoot deploys in realtime while your actions are running. Now, GitHub is also going to allow you to store secrets within the repository for additional safety and ease of use across team members. Actions has a very strong community of developers with hundreds of prebuilt actions, examples and workflows so you don't have to start from scratch. So if you like what you're hearing, then let's get started.