Example branch/foo

.github/workflows/03-core-features--01-hello-world.yaml

@@ -0,0 +1,10 @@
+name: Hello World
+
+on:
+  workflow_dispatch:
+
+jobs:
+  say-hello-inline-bash:
+    runs-on: ubuntu-24.04
+    steps:
+      - run: echo "Hello from an inline bash script in a GitHub Action Workflow!"

.github/workflows/01-hello-world.yaml → .github/workflows/03-core-features--02-step-types.yaml

@@ -1,19 +1,24 @@
-name: Hello World
+name: Step Types
+
 on:
-  # push:
-  #   branches:
-  #     - main
   workflow_dispatch:
+
 jobs:
-  say-hello-inline:
+  say-hello-inline-bash:
     runs-on: ubuntu-24.04
     steps:
       - run: echo "Hello from an inline bash script in a GitHub Action Workflow!"
 
+  say-hello-inline-python:
+    runs-on: ubuntu-24.04
+    steps:
+      - run: print("Hello from an inline python script in a GitHub Action Workflow!")
+        shell: python
+
   say-hello-action:
     runs-on: ubuntu-24.04
     steps:
-      - uses: actions/hello-world-javascript-action@e76147da8e5c81eaf017dede5645551d4b94427b # v1.2.3
+      - uses: actions/hello-world-javascript-action@081a6d193d1dcb38460df1e6927486d748730f9d # v1.1
         # - uses: actions/hello-world-javascript-action@v1 # This would work, but it would be less stable and less secure:
         with:
           who-to-greet: "from an action in the GitHub Action marketplace! 👋"

.github/workflows/03-triggers.yaml → .github/workflows/03-core-features--04-triggers-and-filters.yaml

@@ -18,9 +18,9 @@ on:
       - reopened
     paths:
       # include markdown files
-      - "02-mechanics-core/filters/*.md"
+      - "03-core-features/filters/*.md"
       # Exclude txt files
-      - "!02-mechanics-core/filters/*.txt"
+      - "!03-core-features/filters/*.txt"
 
   ### https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#schedule
   # schedule:

.github/workflows/03-core-features--05-environment-variables.yaml

@@ -0,0 +1,34 @@
+name: Environment Variables
+on:
+  workflow_dispatch:
+env:
+  WORKFLOW_VAR: I_AM_WORKFLOW_SCOPED
+
+jobs:
+  job-1:
+    runs-on: ubuntu-24.04
+    env:
+      JOB_VAR: I_AM_JOB_1_SCOPED
+    steps:
+      - name: Inspect scopes job 1 step 1
+        env:
+          STEP_VAR: I_AM_STEP_SCOPED
+        run: |
+          echo "WORKFLOW_VAR: $WORKFLOW_VAR"   # visible
+          echo "JOB_VAR:      $JOB_VAR"        # visible
+          echo "STEP_VAR:     $STEP_VAR"       # visible only here
+
+      - name: Inspect scopes job 1 step 2
+        run: |
+          echo "WORKFLOW_VAR: $WORKFLOW_VAR"         # visible
+          echo "JOB_VAR:      $JOB_VAR"              # visible
+          echo "STEP_VAR:     ${STEP_VAR:-<UNSET>}"  # not set here
+
+  job-2:
+    runs-on: ubuntu-24.04
+    steps:
+      - name: Inspect scopes job 2 step 2
+        run: |
+          echo "WORKFLOW_VAR: $WORKFLOW_VAR"                 # still visible
+          echo "JOB_VAR:      ${FOO:-<UNSET>}"               # not set here
+          echo "STEP_VAR:     ${STEP_VAR:-<UNSET>}"          # not set here

.github/workflows/03-core-features--06-passing-data.yaml

@@ -0,0 +1,35 @@
+name: Passing Variables Between jobs
+on:
+  workflow_dispatch:
+
+jobs:
+  producer:
+    runs-on: ubuntu-24.04
+
+    outputs:
+      foo: ${{ steps.generate-foo.outputs.foo }}
+    steps:
+      - name: Generate and export foo
+        id: generate-foo
+        run: |
+          foo=bar
+
+          # 1) Step output (for job output)
+          echo "foo=${foo}" >> "$GITHUB_OUTPUT"
+
+          # 2) Job-scoped environment variable
+          echo "FOO=${foo}" >> "$GITHUB_ENV"
+
+      - name: Inspect values inside producer
+        run: |
+          echo "FOO (set via GITHUB_ENV):   $FOO"
+          echo "foo (step output):          ${{ steps.generate-foo.outputs.foo }}"
+
+  consumer:
+    runs-on: ubuntu-24.04
+    needs: producer
+    steps:
+      - name: Inspect values inside consumer (note FOO is unset)
+        run: |
+          echo "Value from producer:        ${{ needs.producer.outputs.foo }}"
+          echo "FOO in consumer:            ${FOO:-<UNSET>}"

.github/workflows/04-passing-data.yaml → .github/workflows/03-core-features--07-secrets-and-variables.yaml

@@ -1,54 +1,9 @@
-name: Environment Vars and Data Passing
+name: Secrets and Environments
 on:
   workflow_dispatch:
 
-env:
-  GLOBAL: THIS_IS_GLOBAL_SCOPED
-
 jobs:
-  job-1:
-    runs-on: ubuntu-24.04
-    env:
-      JOB_1: THIS_IS_JOB_1_SCOPED
-
-    # Make foo available to other jobs
-    outputs:
-      foo: ${{ steps.generate-foo.outputs.foo }}
-
-    steps:
-      - name: Generate and export foo
-        id: generate-foo
-        run: |
-          foo=bar
-
-          # 1) Step output (for job output)
-          echo "foo=${foo}" >> "$GITHUB_OUTPUT"
-
-          # 2) Job-scoped environment variable
-          echo "FOO=${foo}" >> "$GITHUB_ENV"
-
-      - name: Inspect values inside job-1
-        run: |
-          echo "GLOBAL (workflow-level):    $GLOBAL"
-          echo "JOB_1 (job-level):          $JOB_1"
-          echo "FOO (set via GITHUB_ENV):   $FOO"
-          echo "foo (step output):          ${{ steps.generate-foo.outputs.foo }}"
-
-  job-2:
-    runs-on: ubuntu-24.04
-    needs: job-1
-    env:
-      JOB_2: THIS_IS_JOB_2_SCOPED
-
-    steps:
-      - name: Inspect values inside job-2 (note FOO is unset)
-        run: |
-          echo "GLOBAL (workflow-level): $GLOBAL"
-          echo "JOB_2 (job-level):       $JOB_2"
-          echo "Value from job-1:        ${{ needs.job-1.outputs.foo }}"
-          echo "FOO in job-2:            ${FOO:-<UNSET>}"
-
-  job-staging:
+  staging-environment:
     runs-on: ubuntu-24.04
     environment: staging
     env:
@@ -58,7 +13,6 @@ jobs:
       # Inject environment-level items into the shell
       EXAMPLE_ENVIRONMENT_SECRET: ${{ secrets.EXAMPLE_ENVIRONMENT_SECRET }}
       EXAMPLE_ENVIRONMENT_VARIABLE: ${{ vars.EXAMPLE_ENVIRONMENT_VARIABLE }}
-
     steps:
       - name: Inspect values inside job
         run: |
@@ -67,7 +21,7 @@ jobs:
           echo "Env secret (masked):     $EXAMPLE_ENVIRONMENT_SECRET"
           echo "Env variable:            $EXAMPLE_ENVIRONMENT_VARIABLE"
 
-  job-production:
+  production-environment:
     runs-on: ubuntu-24.04
     environment: production
     env:
@@ -77,25 +31,10 @@ jobs:
       # Inject environment-level items into the shell
       EXAMPLE_ENVIRONMENT_SECRET: ${{ secrets.EXAMPLE_ENVIRONMENT_SECRET }}
       EXAMPLE_ENVIRONMENT_VARIABLE: ${{ vars.EXAMPLE_ENVIRONMENT_VARIABLE }}
-
     steps:
       - name: Inspect values inside job
         run: |
           echo "Repo secret (masked):    $EXAMPLE_REPOSITORY_SECRET"
           echo "Repo variable:           $EXAMPLE_REPOSITORY_VARIABLE"
           echo "Env secret (masked):     $EXAMPLE_ENVIRONMENT_SECRET"
           echo "Env variable:            $EXAMPLE_ENVIRONMENT_VARIABLE"
-
-  job-artifact:
-    runs-on: ubuntu-24.04
-    steps:
-      - name: Create artifact file
-        run: |
-          echo "This will be stored as an artifact!" > artifact.txt
-          echo "Generated by job-artifact on $(date)" >> artifact.txt
-
-      - name: Upload artifact
-        uses: actions/upload-artifact@v4
-        with:
-          name: example-artifact
-          path: artifact.txt

.github/workflows/04-advanced-features--01-runner-types.yaml

@@ -0,0 +1,101 @@
+name: Runner types
+on:
+  workflow_dispatch:
+
+jobs:
+  ######################################
+  #  GITHUB (MICROSOFT) HOSTED RUNNERS
+  ######################################
+  #  GitHub provides hosted runners which run on Microsoft Azure.
+  #  
+  #  Open source projects get some free usage and pro/team/enterprise GitHub
+  #  subscriptions also come with some number of minutes included (after which
+  #  you pay based on usage.
+  #   
+  #  These are the easiest to get started with (require no additional configuration
+  #  and it makes sense to use the free minutes, but only on workflows which are not in the
+  #  critical path for your production deployments. For usage beyond your quota I suggest
+  #  looking at the below options for higher performance (and more affordable)
+  #  approaches!
+  ######################################
+  github-hosted-ubuntu-vm:
+    name: Ubuntu 24.04 VM
+    runs-on: ubuntu-24.04
+    steps:
+      - name: Show runner info
+        run: |
+          echo "Hello from ${{ runner.os }}-${{ runner.arch }}"
+          echo "Runner name (type): ${{ runner.name }}"
+
+  github-hosted-windows-vm:
+    name: Windows 2022 VM
+    runs-on: windows-2022
+    steps:
+      - name: Show runner info
+        shell: pwsh
+        run: |
+          echo "Hello from ${{ runner.os }}-${{ runner.arch }}"
+          echo "Runner name (type): ${{ runner.name }}"
+
+  github-hosted-macos-vm:
+    name: macOS 14 VM
+    runs-on: macos-14
+    steps:
+      - name: Show runner info
+        run: |
+          echo "Hello from ${{ runner.os }}-${{ runner.arch }}"
+          echo "Runner name (type): ${{ runner.name }}"
+
+  alpine-container-on-github-hosted-ubuntu-vm:
+    name: Alpine container on Ubuntu VM
+    runs-on: ubuntu-24.04
+    container:
+      image: alpine:3.20
+    steps:
+      - name: Show runner info
+        run: |
+          echo "Hello from ${{ runner.os }}-${{ runner.arch }}"
+          echo "Runner name (type): ${{ runner.name }}"
+          echo "Container image:   $(grep PRETTY_NAME /etc/os-release)"
+
+  ######################################
+  #  3RD PARTY HOSTED RUNNERS
+  ######################################
+  #  There are companies which host GitHub Action runners that provide increased performance for less $$$
+  # 
+  #  One such company happens to be the sponsor of the course! 🙏
+  # 
+  #  ✨ Namespace Labs (https://namespace.so/) ✨
+  #
+  #  You can likely cut your build times (and your CI bill) signiticantly by using their runners
+  #  and it only takes changing a single line of yaml:
+  #  
+  #  - runs-on: ubuntu-24.04 
+  #  + runs-on: namespace-profile-default # The default as of July 2025 is Ubuntu 22.04
+  #
+  #  (They also offer MacOS and Windows runners!)
+  ######################################
+  namespace-ubuntu-vm:
+    name: Namespace Ubuntu VM
+    runs-on: namespace-profile-default
+    steps:
+      - name: Show runner info
+        run: |
+          echo "Hello from ${{ runner.os }}-${{ runner.arch }}"
+          echo "Runner name (type): ${{ runner.name }}"
+
+  ######################################
+  #  SELF HOSTED RUNNERS
+  ######################################
+  #  There are also methods to self-host github action runners.
+  #
+  #  These can provide inexpensive compute, but with increased operational overhead.
+  #  They also allow you to execute within your own VPC which may or may not be important to you depending on your business
+  # 
+  #  A few of the most popular options for doing this:
+  #    - https://runs-on.com/ (run jobs as EC2 instances in AWS)
+  #    - https://github.com/actions/actions-runner-controller (run jobs in any Kubernetes cluster)
+  #    - https://docs.railway.com/tutorials/github-actions-runners (run jobs on Railway)
+  # 
+  #  Configuration/usage of these is outside the scope of this course, and is left as an exercise for the reader
+  ######################################

.github/workflows/04-advanced-features--02-artifacts.yaml

@@ -0,0 +1,32 @@
+name: Artifacts
+on:
+  workflow_dispatch:
+
+jobs:
+  artifact-producer:
+    name: Produce artifact
+    runs-on: ubuntu-24.04
+    steps:
+      - name: Create artifact file
+        run: |
+          echo "This will be stored as an artifact!" > artifact.txt
+          echo "Generated by artifact-producer job on $(date)" >> artifact.txt
+
+      - name: Upload artifact
+        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
+        with:
+          name: example-artifact
+          path: artifact.txt
+
+  artifact-consumer:
+    name: Consume artifact
+    runs-on: ubuntu-24.04
+    needs: artifact-producer
+    steps:
+      - name: Download artifact
+        uses: actions/download-artifact@634f93cb2916e3fdff6788551b99b062d0335ce0 # v5.0.0
+        with:
+          name: example-artifact
+
+      - name: Cat artifact file
+        run: cat artifact.txt