Skip to main content

GitHub Actions CI on Morph

tl;dr Morph Actions is currently a web UI-first product. Use Actions to connect GitHub, open a migration PR, launch workflow_dispatch runs, and inspect logs plus analytics from one org-scoped console.

GitHub Actions CI on Morph

When this product is a good fit​

Morph Actions is a strong fit when your team wants:

  • GitHub-native workflows to stay in GitHub
  • self-hosted jobs to run on Morph-managed infrastructure
  • an org-scoped setup and operations surface
  • live run details, events, logs, and CI analytics in one place

The product flow​

  1. Open Actions.
  2. Install the Morph GitHub App for the repositories you want to run on Morph.
  3. Let Morph generate a workflow migration PR for a selected repository.
  4. Review and merge that PR in GitHub.
  5. Return to the web UI and either click Start New Run or wait for the next normal GitHub trigger.
  6. Expand a run in Runs to inspect metadata, events, and logs.
  7. Open Analytics for the org-level CI view.

Example workflow shape​

One of the simplest Morph-compatible patterns is a workflow_dispatch smoke job that targets the Morph label set:

name: Actions Runner V2 Smoke

on:
  workflow_dispatch:

jobs:
  smoke:
    runs-on: [self-hosted, linux, x64, morph, large]
    steps:
      - uses: actions/checkout@v4
      - run: |
          echo "runner_name=$RUNNER_NAME"
          echo "github_ref=$GITHUB_REF"
          echo "github_sha=$GITHUB_SHA"
          date -u

Morph's migration flow exists so you do not have to hand-edit every workflow up front. The preferred path is still to let the web product propose the PR, then review the diff in GitHub.

What this example demonstrates​

  • org-scoped GitHub App install and repository sync
  • workflow migration PRs instead of silent workflow rewrites
  • Morph runner labels such as self-hosted, linux, x64, morph, and a runner shape
  • run operations centered in the web UI
  • live inspection for historical and active runs

Why teams use Morph Actions​

  • Keep GitHub-native workflow semantics: your workflow files and triggers stay in GitHub.
  • Move execution onto Morph: once labels match, Morph runner-v2 claims the self-hosted job.
  • Review workflow changes safely: setup happens through an explicit migration PR.
  • Operate CI from one surface: run history, live logs, and analytics live in the same product UI.

Up to 30-40% cheaper than industry-leading alternatives​

Morph Actions can be up to 30-40% cheaper than industry-leading alternatives while still keeping GitHub-native workflows, Morph-managed infrastructure, and a single web UI centered on runs and analytics.