diff --git a/serverless/workers/github-integration.mdx b/serverless/workers/github-integration.mdx index 589f2802..0ce00716 100644 --- a/serverless/workers/github-integration.mdx +++ b/serverless/workers/github-integration.mdx @@ -91,74 +91,6 @@ To set up multiple environments: Each environment maintains independent GPU and worker configurations. -## Continuous integration with GitHub Actions - -You can enhance your workflow with GitHub Actions for testing before deployment: - -1. Create a workflow file at `.github/workflows/test-and-deploy.yml`: - - ```yml - name: Test and Deploy - - on: - push: - branches: [ main ] - pull_request: - branches: [ main ] - - jobs: - test-and-deploy: - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@v3 - - - name: Build and push Docker image - uses: docker/build-push-action@v4 - with: - context: . - push: true - tags: [DOCKER_USERNAME]/[WORKER_NAME]:${{ github.sha }} - - - name: Run Tests - uses: runpod/runpod-test-runner@v1 - with: - image-tag: [DOCKER_USERNAME]/[WORKER_NAME]:${{ github.sha }} - runpod-api-key: ${{ secrets.RUNPOD_API_KEY }} # Add your API key to a GitHub secret - test-filename: .github/tests.json - request-timeout: 300 - ``` - - - TIP - - To add your RunPod API key to a GitHub secret, see [Using secrets in GitHub Actions](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions). - - - -2. Create test cases for your repository at `.github/tests.json`: - - ```json - [ - { - "input": { - "prompt": "Test input 1" - }, - "expected_output": { - "status": "COMPLETED" - } - }, - { - "input": { - "prompt": "Test input 2", - "parameter": "value" - }, - "expected_output": { - "status": "COMPLETED" - } - } - ] - ``` - ## Limitations RunPod's GitHub integration has a few limitations you should be aware of: