Closed wlhutchison closed 2 years ago
Great job adding the workflow. Adding that file to this branch is enough for GitHub Actions to begin running on your repository. The time this takes will vary based on the complexity of the workflow. While this runs I'll briefly explain the components of the workflow you just added.
If you want to inspect your running workflow you can do so by heading over to the Actions tab of this repository.
GitHub Actions is a unique world that lives alongside your repository. It is one made up of many moving parts and having a general understanding of these parts will help us understand the behavior we are going to program into our action.
From 30,000 feet GitHub Actions is made up of the following components, with each component having its own complexities:
Component | Description |
---|---|
Action | Individual tasks that you combine as steps to create a job. Actions are the smallest portable building block of a workflow. To use an action in a workflow, you must include it as a step. |
Artifact | Artifacts are the files created when you build and test your code. Artifacts might include binary or package files, test results, screenshots, or log files. Artifacts can be used by the other jobs in the workflow or deployed directly by the workflow. |
Event | A specific activity that triggers a workflow run. |
Job | A defined task made up of steps. Each job is run in a fresh instance of the virtual environment. Jobs can run at the same time in parallel or be dependent on the status of a previous job and run sequentially. |
Runner | Any machine with the GitHub Actions runner application installed. You can use a runner hosted by GitHub or host your own runner. A runner waits for available jobs. Runners run one job at a time reporting the progress, logs, and final result back to GitHub. |
Step | A step is a set of tasks performed by a job. Steps can run commands or actions. |
Virtual Environment | The virtual environment of a GitHub-hosted runner includes the virtual machine's hardware configuration, operating system, and installed software. |
Workflow | A configurable automated process that you can set up in your repository. Workflows are made up of one or more jobs and can be scheduled or activated by an event. |
When a repository is configured with a workflow file, like we just created, the following series of events occurs.
I'm glad you asked. Let's take a look at a workflow file similar to what we just committed to this repository.
name: CI
on: [push]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
- name: Run a one-line script
run: echo Hello, world!
- name: Run a multi-line script
run: |
echo Add other actions to build,
echo test, and deploy your project.
This file is made up of a series of metadata, as well as behaviors that we wish to happen when the workflow is triggered.
Let's take a second to talk about each of the pieces that we see here:
name: CI
CI
on: [push]
Jobs:
build
runs-on: ubuntu-latest
uses: actions/checkout@v1
name: Run a one-line script
run: echo Hello, world!
name: Run a multi-line script
run: |
echo Add other actions to build,
echo test, and deploy your project.
📖Take a deeper dive into workflow components 📖Read more about configuring workflows
if you don't see a response from me below this, try making a new commit to this branch. Your workflow may have finished before I was ready to listen
Oh no... I found an error ⚠️
Error The title of this pull request isn't what I expected!
Solution Verify the name of your pull request is Create a workflow and keep in mind that this is case-sensitive.
Follow these steps to rename your pull request:
I'll respond when I detect this pull request has been renamed.