GloriousFlywheel

Cross-Forge CI

GloriousFlywheel supports both GitLab CI and GitHub Actions from the same Kubernetes cluster. This guide shows equivalent configurations side by side.

Quick Comparison

Feature	GitLab CI	GitHub Actions
Config file	.gitlab-ci.yml	.github/workflows/*.yml
Runner selection	tags: [docker]	runs-on: tinyland-docker
Scaling	HPA (always-warm)	ARC (scale-to-zero)
Cache access	Auto-injected env vars	Auto-injected env vars
Reusable configs	CI/CD Components	Composite Actions
CLI tool	glab	gh

Equivalent Jobs

Simple Build

GitLab CI:

build:
  tags: [docker]
  script:
    - make build

GitHub Actions:

jobs:
  build:
    runs-on: tinyland-docker
    steps:
      - uses: actions/checkout@v4
      - run: make build

Nix Build with Cache

GitLab CI:

build:
  tags: [nix]
  script:
    - nix build .#default
    - attic push main result

GitHub Actions:

jobs:
  build:
    runs-on: tinyland-nix
    steps:
      - uses: actions/checkout@v4
      - uses: tinyland-inc/GloriousFlywheel/.github/actions/nix-job@main
        with:
          command: nix build .#default
          push-cache: "true"

Docker Image Build

GitLab CI:

build-image:
  tags: [dind]
  services:
    - docker:dind
  script:
    - docker build -t $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA .
    - docker push $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA

GitHub Actions:

jobs:
  build-image:
    runs-on: tinyland-dind
    steps:
      - uses: actions/checkout@v4
      - run: |
          docker build -t ghcr.io/$:$ .
          docker push ghcr.io/$:$

CLI Commands

Pipeline / Workflow Status

# GitLab
glab ci status
glab ci view

# GitHub
gh run list
gh run view <run-id>

Create Merge Request / Pull Request

# GitLab
glab mr create --fill --squash-before-merge

# GitHub
gh pr create --fill

View CI Logs

# GitLab
glab ci trace

# GitHub
gh run view <run-id> --log

When to Use Which Forge

Scenario	Recommended Forge	Reason
IaC changes (this repo)	GitLab	State backend on GitLab, CI/CD Components
Open source projects	GitHub	Community visibility, Actions marketplace
Private org projects	Either	Both have full runner access
Nix builds	Either	Both use the same Attic cache

See Also

• GitHub App Adoption – install GloriousFlywheel on your org
• Self-Service Enrollment – GitLab runner enrollment
• GitHub Actions Runners – ARC runner details

This site is open source. Improve this page.