skills · chriswblake · May 28, 2025 · May 27, 2025 · May 27, 2025 · May 28, 2025
diff --git a/.github/steps/-step.txt b/.github/steps/-step.txt
diff --git a/.github/steps/0-welcome.md b/.github/steps/0-welcome.md
diff --git a/.github/steps/1-create-a-workflow.md b/.github/steps/1-create-a-workflow.md
diff --git a/.github/steps/1-step.md b/.github/steps/1-step.md
@@ -0,0 +1,48 @@
+## Step 1: Create a workflow file
+
+### 📖 Theory: Introduction to workflows
+
+A **workflow** is an automated process that you define in your repository. Workflows are described in YAML files stored in the `.github/workflows` directory. Each workflow is triggered by specific [events](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows) happening in your repository such as opening a pull request, pushing code, or creating an issue.
+
+Workflows let you automate tasks like building, testing, or deploying your code, and can respond to almost any activity in your project.
+
+> [!NOTE]
+> If you want to learn more check out these resources:
+> - [Understanding GitHub Actions](https://docs.github.com/en/actions/learn-github-actions/understanding-github-actions)
+> - [Events that trigger workflows](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows)
+
+### ⌨️ Activity: Create a workflow file
+
+1. Open this repository in a new browser tab so you can work on the steps while you read the instructions in this tab.
+
+1. In the **Code** tab of your repository, create a new branch named `welcome-workflow`.
+
+   <img width="400" alt="create branch screenshot" src="https://github.com/user-attachments/assets/8aa4a918-c877-4214-9efe-c9a99ca6421b" />
+
+1. In the `welcome-workflow` branch, navigate to the `.github/workflows` directory.
+
+1. Create a new file named `welcome.yml` in the `.github/workflows` directory with the following content:
+
+   ```yaml
+   name: Post welcome comment
+   on:
+     pull_request:
+       types: [opened]
+   permissions:
+     pull-requests: write
+   ```
+
+   > [!NOTE]
+   > This is an incomplete workflow file. It is normal if you receive an error message. One step at a time! 😎
+
+1. Commit your changes directly to the `welcome-workflow` branch.
+
+1. With your workflow file committed, Mona will check your work and prepare the next step in this exercise!
+
+<details>
+<summary>Having trouble? 🤷</summary><br/>
+
+- Make sure you are on the `welcome-workflow` branch when creating the workflow file.
+- Double-check the file path and YAML indentation.
+
+</details>
diff --git a/.github/steps/2-add-a-job.md b/.github/steps/2-add-a-job.md
diff --git a/.github/steps/2-step.md b/.github/steps/2-step.md
@@ -0,0 +1,43 @@
+## Step 2: Add a job to your workflow file
+
+Nice work! :tada: You added a workflow file!
+
+### 📖 Theory: Introduction to jobs
+
+A [job](https://docs.github.com/en/actions/about-github-actions/understanding-github-actions#jobs) is a group of steps that run together on the same [runner](https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners) within a workflow. Each job is defined under the `jobs` section and runs independently and in parallel by default.
+
+Jobs help you organize your workflow into logical units, such as building, testing, or deploying your code.
+
+> [!Tip]
+> You can define a job to run with multiple [variations using a matrix strategy](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/running-variations-of-jobs-in-a-workflow).
+
+### ⌨️ Activity: Add a job to your workflow file
+
+1. In the `welcome-workflow` branch, open your `.github/workflows/welcome.yml` file.
+
+1. Edit the file to add the `jobs` section and 1 job named `welcome`, which will run on the latest Ubuntu operating system.
+
+   ```yaml
+   name: Post welcome comment
+   on:
+     pull_request:
+       types: [opened]
+   permissions:
+     pull-requests: write
+   jobs:
+     welcome:
+       name: Post welcome comment
+       runs-on: ubuntu-latest
+   ```
+
+1. Commit your changes to the `welcome-workflow` branch.
+
+1. With the job information added, Mona will review your work and prepare the next step in this exercise!
+
+<details>
+<summary>Having trouble? 🤷</summary><br/>
+
+- Make sure the `jobs` section is properly indented in your YAML file.
+- Confirm you are editing the correct file and branch.
+
+</details>
diff --git a/.github/steps/3-add-actions.md b/.github/steps/3-add-actions.md
diff --git a/.github/steps/3-step.md b/.github/steps/3-step.md
@@ -0,0 +1,46 @@
+## Step 3: Add a step to your workflow file
+
+_Nice work adding a job to your workflow! :dancer:_
+
+### 📖 Theory: Introduction to steps in jobs
+
+[Steps](https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#jobsjob_idsteps) are the building blocks of jobs, allowing you to automate tasks like checking out code, running commands, or using open source Actions. They run sequentially in the job's environment but as independent processes. Unlike traditional code with a shared variable space, [inputs](https://docs.github.com/en/actions/sharing-automations/creating-actions/metadata-syntax-for-github-actions#inputs) and [outputs](https://docs.github.com/en/actions/sharing-automations/creating-actions/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions) must be explicitly declared.
+
+> [!TIP]
+> The best part of GitHub Actions is the [marketplace](https://github.com/marketplace?type=actions) where the community has already built many free useful tools to [find and customize](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/using-pre-written-building-blocks-in-your-workflow)!
+
+### ⌨️ Activity: Add a step to your workflow file
+
+1. In the `welcome-workflow` branch, open your `.github/workflows/welcome.yml` file.
+
+1. Add a step to the `welcome` job to post a comment on new pull requests using GitHub CLI:
+
+   ```yaml
+   name: Post welcome comment
+   on:
+     pull_request:
+       types: [opened]
+   permissions:
+     pull-requests: write
+   jobs:
+     welcome:
+       name: Post welcome comment
+       runs-on: ubuntu-latest
+       steps:
+         - run: gh pr comment "$PR_URL" --body "Welcome to the repository!"
+           env:
+             GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+             PR_URL: ${{ github.event.pull_request.html_url }}
+   ```
+
+1. Commit your changes directly to `welcome-workflow` branch.
+
+1. With the step information added, Mona will review your work and prepare the next step in this exercise!
+
+<details>
+<summary>Having trouble? 🤷</summary><br/>
+
+- Make sure the `steps` section is under the `welcome` job and properly indented.
+- Ensure you have the correct environment variables set.
+
+</details>
diff --git a/.github/steps/4-merge-your-pull-request.md b/.github/steps/4-merge-your-pull-request.md
diff --git a/.github/steps/4-step.md b/.github/steps/4-step.md
@@ -0,0 +1,42 @@
+## Step 4: Trigger the workflow
+
+_You've now added a fully functioning workflow to your repository! :smile:_
+
+### 📖 Theory: Seeing your workflow in action
+
+All the running and finished workflows can be seen on the **Actions** tab of your repository.
+
+Because you set the workflow to run on the `pull_request` event, it will automatically trigger when a pull request is opened.
+
+> [!TIP]
+> Workflow associated to pull request can also be seen on the pull request log near the merge button. You can even [create a rule](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets#require-status-checks-to-pass-before-merging) that prevents merging if the workflow fails! 
+
+### ⌨️ Activity: Trigger the workflow
+
+1. In the **Pull requests** tab, create a pull request from `welcome-workflow` branch into `main`.
+
+1. Notice the comment that the workflow adds to the pull request.
+
+1. Notice the area near the merge button that "All checks have passed".
+
+1. With the pull request created and our workflow triggered, Mona will prepare the next step in this exercise!
+
+### ⌨️ Activity: (optional) Inspect the workflow
+
+1. At the top of the repository, select the **Actions** tab.
+
+1. In the left sidebar, select the workflow named **Post welcome comment**.
+
+  > 💡 **Tip:** You can ignore the other actions. Those were for teaching this exercise.
+
+1. Click the first run entry titled **Welcome workflow** to show a diagram of the run's jobs.
+
+1. Click on the job named **Post welcome comment** to see the full logs.
+
+
+<details>
+<summary>Having trouble? 🤷</summary><br/>
+
+- Check the **Actions** tab for workflow run details and errors.
+
+</details>
diff --git a/.github/steps/5-step.md b/.github/steps/5-step.md
@@ -0,0 +1,19 @@
+## Step 5: Merge and experiment
+
+_Great job! You have created and tested your first GitHub Actions workflow!_ :rocket:
+
+### 📖 Theory: When workflows run
+
+When you create a workflow in a branch, it is only enabled for that branch until you merge it into the default branch (`main`). When a workflow is in the default branch it applies to the entire repository.
+
+Every new pull request regardless of branch will now automatically trigger the workflow you created.
+
+> [!TIP]
+> Some event triggers, like [workflow_dispatch](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#workflow_dispatch) and [schedule](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#schedule) will only work if the workflow file exists in default branch. 
+
+### ⌨️ Activity: Merging your pull request
+
+1. Merge your pull request into the `main` branch.
+
+1. (Optional) Try opening another pull request to see your workflow run again!
+
diff --git a/.github/steps/5-trigger.md b/.github/steps/5-trigger.md