协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
firecrawl-ci-integration【开发与工程】Configure FireCrawl CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating FireCrawl tests into your build process. Trigger with phrases like "firecrawl CI", "firecrawl GitHub Actions", "firecrawl automated tests", "CI firecrawl".
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Set up CI/CD pipelines for FireCrawl integrations with automated testing.
Create .github/workflows/firecrawl-integration.yml:
name: FireCrawl Integration Tests
on:
push:
branches: [main]
pull_request:
branches: [main]
env:
FIRECRAWL_API_KEY: ${{ secrets.FIRECRAWL_API_KEY }}
jobs:
test:
runs-on: ubuntu-latest
env:
FIRECRAWL_API_KEY: ${{ secrets.FIRECRAWL_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
gh secret set FIRECRAWL_API_KEY --body "sk_test_***"
describe('FireCrawl Integration', () => {
it.skipIf(!process.env.FIRECRAWL_API_KEY)('should connect', async () => {
const client = getFireCrawlClient();
const result = await client.healthCheck();
expect(result.status).toBe('ok');
});
});
| 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 |
on:
push:
tags: ['v*']
jobs:
release:
runs-on: ubuntu-latest
env:
FIRECRAWL_API_KEY: ${{ secrets.FIRECRAWL_API_KEY_PROD }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
- run: npm ci
- name: Verify FireCrawl production readiness
run: npm run test:integration
- run: npm run build
- run: npm publish
required_status_checks:
- "test"
- "firecrawl-integration"
For deployment patterns, see firecrawl-deploy-integration.