-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Start here! #1
Comments
Setup a workflow file⌨️ Activity: Create a pull request to add a workflow
It is important to place meaningful content into the body of the pull requests you create throughout this course. This repository will stay with you long after you complete the course. It is advisable that you use the body of the pull requests you create as a way to take long lived notes about thing you want to remember. Suggested body content
I'll respond in the new pull request when I detect it has been created. If at any point you're expecting a response and don't see one, refresh the page. |
A new pull requestNow, let's move to the new pull request where we will continue this lesson. Click the link to meet me over there. |
Hi there 👋!
Hello @Cemberk, I'm so excited to teach you how to create your own custom Docker based action 😄
GitHub Actions are enabled on your repository by default, but we still have to tell our repository to use them. We do this by creating a workflow file in our repository.
What is a workflow file?
A workflow file can be thought of as the recipe for automating a task. They house the start-to-finish instructions, in the form of
jobs
andsteps
, for what should happen based on specific triggers.Your repository can contain multiple workflow files that carry out a wide variety of tasks. It is important to consider this when deciding on a name for your workflow. The name you choose should reflect the tasks being performed.
In our case, we will use this one workflow file for many things, which leads us to break this convention for teaching purposes.
📖 Read more about workflows
The text was updated successfully, but these errors were encountered: