Deploying To Staging Environment

This orchestrates staging deployments across three interdependent repos (relay, relay-dashboard, relay-cloud) using git worktrees to keep your working directory clean while syncing branches. You push main or feature branches to staging in each repo, and when relay-cloud's staging branch updates, it automatically triggers GitHub Actions to deploy everything to Fly.io with health checks. The worktree approach is solid engineering, isolating the staging push operation so you don't accidentally pollute your current work. Main gotcha is remembering that only relay-cloud triggers the actual deployment, so you need to coordinate all three repos or manually override branch references in the GitHub workflow. Best for multi-repo feature integration where changes span components.

GitHub stars: 719
last updated: Jun 11, 2026

View on GitHub

Install

$ npx -y skills add agentworkforce/relay --skill deploying-to-staging-environment --agent claude-code

Installs into .claude/skills of the current project.

Files

Deploying to Staging Environment

Overview

The staging environment deployment is a coordinated multi-repo process that synchronizes code across three repositories (relay, relay-dashboard, relay-cloud) and automatically triggers deployment via GitHub Actions. Staging deployments ensure feature verification before production while keeping main branch clean during development.

When to Use

Integrating features across repos - Multiple components depend on changes in different repos
Testing feature branches together - Verify feature branch changes don't break integration
Promoting main to staging - Standard sync to keep staging up-to-date with latest main
Verifying deployment readiness - Test infrastructure changes or deployment workflows
Cross-team coordination - Share feature branches for integration testing

When NOT to use: