replit-ci-integration
Configure CI/CD for Replit with GitHub Actions, automated testing, and deploy-on-push. Use when setting up automated testing, GitHub integration for Replit, or continuous deployment pipelines that deploy to Replit. Trigger with phrases like "replit CI", "replit GitHub Actions", "replit automated deploy", "CI replit", "replit GitHub".
What this skill does
# Replit CI Integration
## Overview
Set up CI/CD for Replit apps: GitHub repo connected to Replit, automated testing via GitHub Actions, deploy-on-push, and post-deploy health verification. Replit supports direct GitHub import and auto-sync.
## Prerequisites
- GitHub repository with Actions enabled
- Replit App connected to GitHub (Settings > Git > Connect)
- GitHub Secrets configured for deploy verification
## Instructions
### Step 1: Connect Replit to GitHub
```markdown
1. In your Repl, click "Git" in the sidebar
2. Click "Connect to GitHub"
3. Authorize Replit GitHub App
4. Select your repository
5. Changes pushed to GitHub auto-sync to Replit
Alternative: Import from GitHub
1. Create new Repl > "Import from GitHub"
2. Paste repo URL
3. Replit clones and configures automatically
```
### Step 2: GitHub Actions — Test on PR
```yaml
# .github/workflows/test.yml
name: Test
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
test:
runs-on: ubuntu-latest
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 lint
- run: npm run build
```
### Step 3: Deploy Verification After Push
Replit auto-deploys when you push to the connected branch. Verify the deployment is healthy:
```yaml
# .github/workflows/deploy-verify.yml
name: Verify Deployment
on:
push:
branches: [main]
jobs:
verify:
runs-on: ubuntu-latest
# Wait for Replit to pick up the push and deploy
steps:
- name: Wait for deployment
run: sleep 60
- name: Health check
run: |
DEPLOY_URL="${{ secrets.REPLIT_DEPLOY_URL }}"
STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$DEPLOY_URL/health")
if [ "$STATUS" != "200" ]; then
echo "Health check failed: HTTP $STATUS"
exit 1
fi
echo "Deployment healthy"
- name: Response time check
run: |
DEPLOY_URL="${{ secrets.REPLIT_DEPLOY_URL }}"
TIME=$(curl -s -o /dev/null -w "%{time_total}" "$DEPLOY_URL/health")
echo "Response time: ${TIME}s"
# Alert if response > 5 seconds (cold start)
if (( $(echo "$TIME > 5" | bc -l) )); then
echo "WARNING: Slow response (possible cold start)"
fi
```
### Step 4: Store Deployment Secrets
```bash
# Set GitHub secrets for deploy verification
gh secret set REPLIT_DEPLOY_URL --body "https://your-app.replit.app"
# Optional: Replit API token for advanced deployments
gh secret set REPLIT_TOKEN --body "your-replit-api-token"
```
### Step 5: Branch Protection
```yaml
# Require tests to pass before merge
# In GitHub: Settings > Branches > Branch protection rules
# Required status checks:
required_status_checks:
- "test"
# Recommended settings:
# - Require pull request reviews before merging
# - Require status checks to pass before merging
# - Require branches to be up to date before merging
```
### Step 6: GitHub Actions — Deploy from GitHub Repo
For repos not directly connected to Replit, deploy via GitHub Import:
```yaml
# .github/workflows/deploy-replit.yml
name: Deploy to Replit
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Run tests first
run: |
npm ci
npm test
npm run build
- name: Trigger Replit deployment
run: |
# Replit auto-deploys from connected GitHub repos
# For manual trigger, use Replit API:
curl -X POST \
"https://replit.com/api/v1/repls/${{ secrets.REPL_ID }}/deploy" \
-H "Authorization: Bearer ${{ secrets.REPLIT_TOKEN }}" \
-H "Content-Type: application/json"
- name: Verify deployment
run: |
sleep 90 # Wait for build + deploy
curl -sf "${{ secrets.REPLIT_DEPLOY_URL }}/health"
```
### Step 7: Python CI Variant
```yaml
# .github/workflows/test-python.yml
name: Test Python
on: [push, pull_request]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: '3.11'
cache: 'pip'
- run: pip install -r requirements.txt
- run: python -m pytest tests/ -v
- run: python -m flake8 .
```
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| GitHub sync not working | App not connected | Reconnect in Replit Git settings |
| Deploy verification timeout | Slow Autoscale cold start | Increase sleep, or use Reserved VM |
| Tests pass but deploy fails | Build step missing | Add `build` to `.replit` deployment section |
| Secret not found in Actions | Not set in GitHub | `gh secret set` with correct name |
## Resources
- [Deploying from GitHub](https://docs.replit.com/hosting/deployments/deploying-a-github-repository)
- [GitHub Actions](https://docs.github.com/en/actions)
- [Replit Git Integration](https://docs.replit.com/replit-workspace/configuring-repl)
## Next Steps
For deployment patterns, see `replit-deploy-integration`.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.