In this repository we will be diving into the world of writing GitHub Actions! I will guide you through the process of writing a custom Docker based GitHub Actions.
You may be asking yourself, "is Docker the only way to create custom GitHub Actions?"
Currently, there are two supported ways to create your own GitHub Actions:
As you can see we aren't necessarily limited to Docker even though it is the focal point for this course.
Although we are going to focus on creating and consuming a custom action, in this course we will also be consuming some actions that have been made public to us. Because your workflows will most likely do the same, I found it important to show you where to look for actions that already exist.
After all, for each time we need to reinvent the wheel for our specific use-case there are a handful of times when we are better off using a wheel that's already made!
[checkout](https://github.com/actions/checkout) from this repository as we go through this course. I'll explain more about what it does when we use it!.github/actions directory in the root of your repository. This is the convention we will be using as we learn how to create our own action.In other courses, you may have noticed that some behaviors take me longer to respond to than others. In this course, many of the behaviors we'll see demonstrated will be related to our GitHub Actions workflow. Those workflows sometimes take longer to complete, up to several minutes. Don't be concerned if I take a few minutes to respond, or if I respond too quickly. Sometimes, I'll let you know what the workflow will say before it finishes! Please wait for the workflows to finish before moving on to your next step.
If you aren't already familiar, it may be a good idea to go through the Introduction to GitHub Learning Lab.
Please navigate to the open issue in this repository to get started!