Configure Vast.ai CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Vast.ai tests into your build process. Trigger with phrases like "vastai CI", "vastai GitHub Actions", "vastai automated tests", "CI vastai".
Scanned 9/10/2026
Install to Claude Code
npx -y skills add micsapp/micstec-skills --skill vastai-ci-integration --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Vastai Ci Integration?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/micsapp-vastai-ci-integration)More formats (shields.io, HTML) on the badges page.
---
name: vastai-ci-integration
description: |
Configure Vast.ai CI/CD integration with GitHub Actions and testing.
Use when setting up automated testing, configuring CI pipelines,
or integrating Vast.ai tests into your build process.
Trigger with phrases like "vastai CI", "vastai GitHub Actions",
"vastai automated tests", "CI vastai".
allowed-tools: Read, Write, Edit, Bash(gh:*)
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
compatible-with: claude-code, codex, openclaw
---
# Vast.ai CI Integration
## Overview
Set up CI/CD pipelines for Vast.ai integrations with automated testing.
## Prerequisites
- GitHub repository with Actions enabled
- Vast.ai test API key
- npm/pnpm project configured
## Instructions
### Step 1: Create GitHub Actions Workflow
Create `.github/workflows/vastai-integration.yml`:
```yaml
name: Vast.ai Integration Tests
on:
push:
branches: [main]
pull_request:
branches: [main]
env:
VASTAI_API_KEY: ${{ secrets.VASTAI_API_KEY }}
jobs:
test:
runs-on: ubuntu-latest
env:
VASTAI_API_KEY: ${{ secrets.VASTAI_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
```bash
gh secret set VASTAI_API_KEY --body "sk_test_***"
```
### Step 3: Add Integration Tests
```typescript
describe('Vast.ai Integration', () => {
it.skipIf(!process.env.VASTAI_API_KEY)('should connect', async () => {
const client = getVast.aiClient();
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
```yaml
on:
push:
tags: ['v*']
jobs:
release:
runs-on: ubuntu-latest
env:
VASTAI_API_KEY: ${{ secrets.VASTAI_API_KEY_PROD }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
- run: npm ci
- name: Verify Vast.ai production readiness
run: npm run test:integration
- run: npm run build
- run: npm publish
```
### Branch Protection
```yaml
required_status_checks:
- "test"
- "vastai-integration"
```
## Resources
- [GitHub Actions Documentation](https://docs.github.com/en/actions)
- [Vast.ai CI Guide](https://docs.vastai.com/ci)
## Next Steps
For deployment patterns, see `vastai-deploy-integration`.Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!