flyio-ci-integration
Configure Fly.io CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Fly.io tests into your build process. Trigger with phrases like "flyio CI", "flyio GitHub Actions", "flyio automated tests", "CI flyio".
claude-code
Allowed Tools
ReadWriteEditBash(gh:*)
Provided by Plugin
flyio-pack
Claude Code skill pack for Fly.io (18 skills)
Installation
This skill is included in the flyio-pack plugin:
/plugin install flyio-pack@claude-code-plugins-plus
Click to copy
Instructions
Fly.io CI Integration
Overview
Set up CI/CD pipelines for Fly.io integrations with automated testing.
Prerequisites
- GitHub repository with Actions enabled
- Fly.io test API key
- npm/pnpm project configured
Instructions
Step 1: Create GitHub Actions Workflow
Create .github/workflows/flyio-integration.yml:
name: Fly.io Integration Tests
on:
push:
branches: [main]
pull_request:
branches: [main]
env:
FLYIO_API_KEY: ${{ secrets.FLYIO_API_KEY }}
jobs:
test:
runs-on: ubuntu-latest
env:
FLYIO_API_KEY: ${{ secrets.FLYIO_API_KEY }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- run: npm ci
- run: npm test -- --coverage
- run: npm run test:integration
Step 2: Configure Secrets
gh secret set FLYIO_API_KEY --body "sk_test_***"
Step 3: Add Integration Tests
describe('Fly.io Integration', () => {
it.skipIf(!process.env.FLYIO_API_KEY)('should connect', async () => {
const client = getFly.ioClient();
const result = await client.healthCheck();
expect(result.status).toBe('ok');
});
});
Output
- Automated test pipeline
- PR checks configured
- Coverage reports uploaded
- Release workflow ready
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Secret not found | Missing configuration | Add secret via gh secret set |
| Tests timeout | Network issues | Increase timeout or mock |
| Auth failures | Invalid key | Check secret value |
Examples
Release Workflow
on:
push:
tags: ['v*']
jobs:
release:
runs-on: ubuntu-latest
env:
FLYIO_API_KEY: ${{ secrets.FLYIO_API_KEY_PROD }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
- run: npm ci
- name: Verify Fly.io production readiness
run: npm run test:integration
- run: npm run build
- run: npm publish
Branch Protection
required_status_checks:
- "test"
- "flyio-integration"
Resources
Next Steps
For deployment patterns, see flyio-deploy-integration.