deploying-to-staging-environment

Coordinates multi-repo staging deployments across relay, relay-dashboard, and relay-cloud using git worktrees and GitHub Actions.

812|65|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/AgentWorkforce/relay --skill deploying-to-staging-environment
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deploying-to-staging-environment
Source: https://github.com/AgentWorkforce/relay/tree/main/.claude/skills/deploying-to-staging-environment
Command: npx skills add https://github.com/AgentWorkforce/relay --skill deploying-to-staging-environment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying to staging requires synchronizing branches across three separate repositories (relay, relay-dashboard, relay-cloud), and mistakes like pushing stale refs or forgetting to trigger the deployment workflow lead to broken or outdated staging environments.

Core Features & Use Cases

  • Multi-Repo Branch Syncing: Push main or feature branches to staging across all three repos using isolated git worktrees.
  • Automatic Deployment Triggering: Pushing relay-cloud staging triggers the deploy-staging.yml GitHub Actions workflow, which deploys to Fly.io and verifies a health check.
  • Branch Override Support: Manually dispatch the workflow with custom relay_branch and dashboard_branch inputs, with automatic fallback to main.
  • Use Case: A feature spans all three repos and needs integration testing. Push each repo's branch to staging via worktrees, then monitor the Deploy (Staging) workflow until the health check at agent-relay-staging.fly.dev returns 200.

Quick Start

Use the staging deployment skill to push the latest main branches of relay, relay-dashboard, and relay-cloud to staging and verify the deployment succeeds.

Frequently Asked Questions about deploying-to-staging-environment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy multiple repos to a staging environment?▼

Push each repo's branch to its staging branch using git worktrees, then push relay-cloud last since its staging push triggers the deploy-staging.yml GitHub Actions workflow. The workflow deploys to Fly.io and runs an automatic health check.

How do I push a feature branch to staging with git worktrees?▼

Create a worktree with git worktree add .worktrees/staging-push main, fetch the feature branch with git fetch origin feature/name:feature/name, then push it with git push origin feature/name:staging. Remove the worktree afterward to keep the repo clean.

Can I deploy specific branches of relay and relay-dashboard to staging?▼

Yes, the deploy-staging.yml workflow accepts optional relay_branch and dashboard_branch inputs via workflow_dispatch. If a specified branch does not exist in the remote, the workflow falls back to main.

Why does my staging deployment fail the health check?▼

The health check times out when the Fly.io app takes too long to become healthy, usually due to build errors or startup failures. Check logs with flyctl logs --app agent-relay-staging and review the failed workflow step.

When should I not use the staging deployment workflow?▼

Avoid it for emergency hotfixes, which should go through production deployment, and for single-repo changes that do not block other repos. It is also unnecessary when testing locally without intent to deploy.