diff --git a/datasets/chat/github_actions/metadata.json b/datasets/chat/github_actions/metadata.json index 5d59cb171..caa772058 100644 --- a/datasets/chat/github_actions/metadata.json +++ b/datasets/chat/github_actions/metadata.json @@ -5,19 +5,19 @@ "generation_seed": 99, "workflows_parsed": 13, "workflow_names": [ - "Aria E2E Tests", - "Auto Validation", - "AzureML LoRA Train", "QAI CI Pipeline", - "Code Quality", - "CodeQL Security Scanning", - "E2E + Integration Tests", + "Workflow Validation", + "Stale Issues and PRs", "Deploy to GitHub Pages", - "PR Checks", + "Aria E2E Tests", + "E2E + Integration Tests", + "AzureML LoRA Train", "Quantum Automation", + "Auto Validation", + "PR Checks", "Release", - "Stale Issues and PRs", - "Workflow Validation" + "CodeQL Security Scanning", + "Code Quality" ], "generation_date": "2026-03-26T17:47:40.871477" } \ No newline at end of file diff --git a/datasets/chat/github_actions/test.json b/datasets/chat/github_actions/test.json index c8ede3298..a969e6b03 100644 --- a/datasets/chat/github_actions/test.json +++ b/datasets/chat/github_actions/test.json @@ -1,3 +1,3 @@ {"messages": [{"role": "user", "content": "What is a matrix strategy in GitHub Actions?"}, {"role": "assistant", "content": "A matrix strategy in GitHub Actions allows you to run a job with multiple configurations automatically:\n\n```yaml\njobs:\n test:\n runs-on: ubuntu-latest\n strategy:\n matrix:\n python-version: ['3.9', '3.10', '3.11', '3.12']\n os: [ubuntu-latest, windows-latest, macos-latest]\n steps:\n - uses: actions/setup-python@v5\n with:\n python-version: ${{ matrix.python-version }}\n - run: python --version\n - run: pytest\n```\n\nThis creates 12 jobs (4 Python versions × 3 OS) automatically.\n\n**Key features**:\n- `${{ matrix.variable }}` accesses matrix values\n- `fail-fast: false` continues other jobs if one fails\n- `max-parallel` limits concurrent jobs\n- `include` adds specific combinations\n- `exclude` removes specific combinations\n\n**Use cases**:\n- Testing across multiple Python/Node versions\n- Cross-platform testing (Linux, Windows, macOS)\n- Testing with different dependency versions\n- Different configuration combinations"}], "source": "general_knowledge", "template": "matrix"} -{"messages": [{"role": "user", "content": "What jobs are defined in the 'Auto Validation' workflow?"}, {"role": "assistant", "content": "The workflow defines 1 job(s):\n\n\n**dry-run**:\n - Runs on: ubuntu-latest\n - Contains 5 step(s)"}], "source_workflow": "Auto Validation", "source_path": ".github/workflows/auto-validation.yml", "template": "jobs", "hash": "510dd0820fe98f3b"} -{"messages": [{"role": "user", "content": "When does the 'Aria E2E Tests' workflow run?"}, {"role": "assistant", "content": "This workflow has no explicit triggers defined."}], "source_workflow": "Aria E2E Tests", "source_path": ".github/workflows/aria-tests.yml", "template": "triggers", "hash": "0b108737ae091f7e"} +{"messages": [{"role": "user", "content": "What jobs are defined in the 'Workflow Validation' workflow?"}, {"role": "assistant", "content": "The workflow defines 2 job(s):\n\n\n**validate-workflows**:\n - Runs on: ubuntu-latest\n - Contains 5 step(s)\n\n**test-workflows**:\n - Runs on: ubuntu-latest\n - Depends on: validate-workflows\n - Contains 3 step(s)"}], "source_workflow": "Workflow Validation", "source_path": ".github/workflows/workflow-validation.yml", "template": "jobs", "hash": "cb9797af5c503cf7"} +{"messages": [{"role": "user", "content": "When does the 'QAI CI Pipeline' workflow run?"}, {"role": "assistant", "content": "This workflow has no explicit triggers defined."}], "source_workflow": "QAI CI Pipeline", "source_path": ".github/workflows/ci-pipeline.yml", "template": "triggers", "hash": "021d60314cdee68f"} diff --git a/datasets/chat/github_actions/train.json b/datasets/chat/github_actions/train.json index e0a3e0e2e..1ff3b9fe8 100644 --- a/datasets/chat/github_actions/train.json +++ b/datasets/chat/github_actions/train.json @@ -1,16 +1,16 @@ -{"messages": [{"role": "user", "content": "What jobs are defined in the 'Aria E2E Tests' workflow?"}, {"role": "assistant", "content": "The workflow defines 5 job(s):\n\n\n**unit-integration-tests**:\n - Runs on: ubuntu-latest\n - Contains 5 step(s)\n\n**playwright-e2e**:\n - Runs on: ubuntu-latest\n - Depends on: unit-integration-tests\n - Contains 9 step(s)\n\n**pyppeteer-e2e**:\n - Runs on: ubuntu-latest\n - Depends on: unit-integration-tests\n - Contains 10 step(s)\n\n**containerized-chrome-e2e**:\n - Runs on: ubuntu-latest\n - Depends on: unit-integration-tests\n - Contains 9 step(s)\n\n**test-summary**:\n - Runs on: ubuntu-latest\n - Depends on: unit-integration-tests, playwright-e2e, pyppeteer-e2e, containerized-chrome-e2e\n - Contains 2 step(s)\n - Conditional: always()"}], "source_workflow": "Aria E2E Tests", "source_path": ".github/workflows/aria-tests.yml", "template": "jobs", "hash": "1477073b6344d5e1"} +{"messages": [{"role": "user", "content": "What jobs are defined in the 'QAI CI Pipeline' workflow?"}, {"role": "assistant", "content": "The workflow defines 3 job(s):\n\n\n**validate**:\n - Runs on: ubuntu-latest\n - Contains 9 step(s)\n\n**train**:\n - Runs on: ubuntu-latest\n - Depends on: validate\n - Contains 5 step(s)\n - Conditional: github.event_name == 'schedule'\n\n**deploy**:\n - Runs on: ubuntu-latest\n - Depends on: train\n - Contains 4 step(s)\n - Conditional: github.event_name == 'schedule'"}], "source_workflow": "QAI CI Pipeline", "source_path": ".github/workflows/ci-pipeline.yml", "template": "jobs", "hash": "4de0d53e900c36c5"} {"messages": [{"role": "user", "content": "What is GitHub Actions?"}, {"role": "assistant", "content": "GitHub Actions is a CI/CD (Continuous Integration/Continuous Deployment) platform built into GitHub that allows you to automate your software development workflows. You can:\n\n- Run tests automatically on every push or pull request\n- Build and deploy applications\n- Automate code quality checks and linting\n- Schedule regular tasks\n- Respond to GitHub events (issues, releases, etc.)\n\nWorkflows are defined in YAML files stored in `.github/workflows/` directory."}], "source": "general_knowledge", "template": "concept"} -{"messages": [{"role": "user", "content": "How do I debug failures in the 'Aria E2E Tests' workflow?"}, {"role": "assistant", "content": "To debug failures in the 'Aria E2E Tests' workflow:\n\n1. **Check the Actions tab**: Go to GitHub Actions tab to see run history\n2. **Review logs**: Click on the failed run and expand failed steps to see detailed logs\n3. **Look for error messages**: Red text usually indicates the failure point\n4. **Verify triggers**: Ensure the workflow triggered as expected (check triggers: none)\n5. **Test locally**: Try running the commands from failed steps on your local machine\n6. **Check dependencies**: Ensure all required dependencies are installed\n7. **Review permissions**: Verify the workflow has necessary permissions\n8. **Use workflow_dispatch**: Add manual trigger for easier testing\n\nCommon issues:\n- Missing environment variables or secrets\n- Incorrect file paths\n- Dependency version conflicts\n- Insufficient permissions\n- Timeout issues (increase with `timeout-minutes`)\n\nFor persistent issues, you can enable debug logging by setting these secrets:\n- ACTIONS_STEP_DEBUG: true\n- ACTIONS_RUNNER_DEBUG: true"}], "source_workflow": "Aria E2E Tests", "source_path": ".github/workflows/aria-tests.yml", "template": "troubleshooting", "hash": "75fb6f3000d1b4ca"} -{"messages": [{"role": "user", "content": "How would I modify the 'Auto Validation' workflow to add a new step?"}, {"role": "assistant", "content": "To add a new step to the 'Auto Validation' workflow:\n\n1. Choose which job to modify (available: dry-run)\n2. Locate the `steps` section within that job\n3. Add a new step with:\n - `name`: A descriptive name for the step\n - `run`: Command(s) to execute, or\n - `uses`: An action to use (e.g., actions/checkout@v4)\n4. Optionally add conditions with `if:` to control when the step runs\n\nExample step structure:\n```yaml\n- name: My new step\n run: |\n echo \"Running my command\"\n python my_script.py\n```\n\nOr using an action:\n```yaml\n- name: Upload results\n uses: actions/upload-artifact@v4\n with:\n name: my-artifact\n path: results/\n```\n\nRemember to test your changes in a feature branch before merging to main."}], "source_workflow": "Auto Validation", "source_path": ".github/workflows/auto-validation.yml", "template": "modification", "hash": "d328c4f201a13de3"} -{"messages": [{"role": "user", "content": "How do I debug failures in the 'Auto Validation' workflow?"}, {"role": "assistant", "content": "To debug failures in the 'Auto Validation' workflow:\n\n1. **Check the Actions tab**: Go to GitHub Actions tab to see run history\n2. **Review logs**: Click on the failed run and expand failed steps to see detailed logs\n3. **Look for error messages**: Red text usually indicates the failure point\n4. **Verify triggers**: Ensure the workflow triggered as expected (check triggers: none)\n5. **Test locally**: Try running the commands from failed steps on your local machine\n6. **Check dependencies**: Ensure all required dependencies are installed\n7. **Review permissions**: Verify the workflow has necessary permissions\n8. **Use workflow_dispatch**: Add manual trigger for easier testing\n\nCommon issues:\n- Missing environment variables or secrets\n- Incorrect file paths\n- Dependency version conflicts\n- Insufficient permissions\n- Timeout issues (increase with `timeout-minutes`)\n\nFor persistent issues, you can enable debug logging by setting these secrets:\n- ACTIONS_STEP_DEBUG: true\n- ACTIONS_RUNNER_DEBUG: true"}], "source_workflow": "Auto Validation", "source_path": ".github/workflows/auto-validation.yml", "template": "troubleshooting", "hash": "ebcc9778f0cf397d"} -{"messages": [{"role": "user", "content": "What GitHub Actions are used in the 'Aria E2E Tests' workflow?"}, {"role": "assistant", "content": "The workflow uses 4 different actions:\n\n- **actions/checkout@v4**: Checks out the repository code\n- **actions/download-artifact@v4**: Downloads previously uploaded artifacts\n- **actions/setup-python@v5**: Sets up a Python environment\n- **actions/upload-artifact@v4**: Uploads build artifacts for later use"}], "source_workflow": "Aria E2E Tests", "source_path": ".github/workflows/aria-tests.yml", "template": "actions", "hash": "696899fa4621c11f"} -{"messages": [{"role": "user", "content": "What does the GitHub Actions workflow 'Aria E2E Tests' do?"}, {"role": "assistant", "content": "The workflow 'Aria E2E Tests' is a CI/CD pipeline that:\n- Contains 5 job(s): unit-integration-tests, playwright-e2e, pyppeteer-e2e, containerized-chrome-e2e, test-summary\n- Uses 4 different GitHub Actions\n\nThis workflow is primarily focused on running automated tests."}], "source_workflow": "Aria E2E Tests", "source_path": ".github/workflows/aria-tests.yml", "template": "overview", "hash": "444c93c7ec75f5ab"} -{"messages": [{"role": "user", "content": "What are the best practices demonstrated in the 'Aria E2E Tests' workflow?"}, {"role": "assistant", "content": "The 'Aria E2E Tests' workflow demonstrates several best practices:\n\n- Uses actions/checkout to ensure clean code access\n- Preserves build artifacts for debugging and deployment\n- Uses job dependencies to create a proper pipeline flow\n- Uses conditional job execution to optimize resource usage\n- Uses matrix strategy for testing across multiple configurations"}], "source_workflow": "Aria E2E Tests", "source_path": ".github/workflows/aria-tests.yml", "template": "best_practices", "hash": "2524595bc41cd145"} -{"messages": [{"role": "user", "content": "How would I modify the 'Aria E2E Tests' workflow to add a new step?"}, {"role": "assistant", "content": "To add a new step to the 'Aria E2E Tests' workflow:\n\n1. Choose which job to modify (available: unit-integration-tests, playwright-e2e, pyppeteer-e2e, containerized-chrome-e2e, test-summary)\n2. Locate the `steps` section within that job\n3. Add a new step with:\n - `name`: A descriptive name for the step\n - `run`: Command(s) to execute, or\n - `uses`: An action to use (e.g., actions/checkout@v4)\n4. Optionally add conditions with `if:` to control when the step runs\n\nExample step structure:\n```yaml\n- name: My new step\n run: |\n echo \"Running my command\"\n python my_script.py\n```\n\nOr using an action:\n```yaml\n- name: Upload results\n uses: actions/upload-artifact@v4\n with:\n name: my-artifact\n path: results/\n```\n\nRemember to test your changes in a feature branch before merging to main."}], "source_workflow": "Aria E2E Tests", "source_path": ".github/workflows/aria-tests.yml", "template": "modification", "hash": "f9d15bc576018586"} -{"messages": [{"role": "user", "content": "What are the best practices demonstrated in the 'Auto Validation' workflow?"}, {"role": "assistant", "content": "The 'Auto Validation' workflow demonstrates several best practices:\n\n- Uses actions/checkout to ensure clean code access\n- Preserves build artifacts for debugging and deployment"}], "source_workflow": "Auto Validation", "source_path": ".github/workflows/auto-validation.yml", "template": "best_practices", "hash": "92f618023e1490b1"} +{"messages": [{"role": "user", "content": "How do I debug failures in the 'QAI CI Pipeline' workflow?"}, {"role": "assistant", "content": "To debug failures in the 'QAI CI Pipeline' workflow:\n\n1. **Check the Actions tab**: Go to GitHub Actions tab to see run history\n2. **Review logs**: Click on the failed run and expand failed steps to see detailed logs\n3. **Look for error messages**: Red text usually indicates the failure point\n4. **Verify triggers**: Ensure the workflow triggered as expected (check triggers: none)\n5. **Test locally**: Try running the commands from failed steps on your local machine\n6. **Check dependencies**: Ensure all required dependencies are installed\n7. **Review permissions**: Verify the workflow has necessary permissions\n8. **Use workflow_dispatch**: Add manual trigger for easier testing\n\nCommon issues:\n- Missing environment variables or secrets\n- Incorrect file paths\n- Dependency version conflicts\n- Insufficient permissions\n- Timeout issues (increase with `timeout-minutes`)\n\nFor persistent issues, you can enable debug logging by setting these secrets:\n- ACTIONS_STEP_DEBUG: true\n- ACTIONS_RUNNER_DEBUG: true"}], "source_workflow": "QAI CI Pipeline", "source_path": ".github/workflows/ci-pipeline.yml", "template": "troubleshooting", "hash": "6bc31608704d660b"} +{"messages": [{"role": "user", "content": "How would I modify the 'Workflow Validation' workflow to add a new step?"}, {"role": "assistant", "content": "To add a new step to the 'Workflow Validation' workflow:\n\n1. Choose which job to modify (available: validate-workflows, test-workflows)\n2. Locate the `steps` section within that job\n3. Add a new step with:\n - `name`: A descriptive name for the step\n - `run`: Command(s) to execute, or\n - `uses`: An action to use (e.g., actions/checkout@v4)\n4. Optionally add conditions with `if:` to control when the step runs\n\nExample step structure:\n```yaml\n- name: My new step\n run: |\n echo \"Running my command\"\n python my_script.py\n```\n\nOr using an action:\n```yaml\n- name: Upload results\n uses: actions/upload-artifact@v4\n with:\n name: my-artifact\n path: results/\n```\n\nRemember to test your changes in a feature branch before merging to main."}], "source_workflow": "Workflow Validation", "source_path": ".github/workflows/workflow-validation.yml", "template": "modification", "hash": "d7e0a69641f36a5a"} +{"messages": [{"role": "user", "content": "How do I debug failures in the 'Workflow Validation' workflow?"}, {"role": "assistant", "content": "To debug failures in the 'Workflow Validation' workflow:\n\n1. **Check the Actions tab**: Go to GitHub Actions tab to see run history\n2. **Review logs**: Click on the failed run and expand failed steps to see detailed logs\n3. **Look for error messages**: Red text usually indicates the failure point\n4. **Verify triggers**: Ensure the workflow triggered as expected (check triggers: none)\n5. **Test locally**: Try running the commands from failed steps on your local machine\n6. **Check dependencies**: Ensure all required dependencies are installed\n7. **Review permissions**: Verify the workflow has necessary permissions\n8. **Use workflow_dispatch**: Add manual trigger for easier testing\n\nCommon issues:\n- Missing environment variables or secrets\n- Incorrect file paths\n- Dependency version conflicts\n- Insufficient permissions\n- Timeout issues (increase with `timeout-minutes`)\n\nFor persistent issues, you can enable debug logging by setting these secrets:\n- ACTIONS_STEP_DEBUG: true\n- ACTIONS_RUNNER_DEBUG: true"}], "source_workflow": "Workflow Validation", "source_path": ".github/workflows/workflow-validation.yml", "template": "troubleshooting", "hash": "9abf96372e198850"} +{"messages": [{"role": "user", "content": "What GitHub Actions are used in the 'QAI CI Pipeline' workflow?"}, {"role": "assistant", "content": "The workflow uses 3 different actions:\n\n- **./.github/actions/setup-python-env**: Performs ./.github/actions/setup-python-env functionality\n- **actions/checkout@v4**: Checks out the repository code\n- **actions/upload-artifact@v4**: Uploads build artifacts for later use"}], "source_workflow": "QAI CI Pipeline", "source_path": ".github/workflows/ci-pipeline.yml", "template": "actions", "hash": "9ef12ad1be21de85"} +{"messages": [{"role": "user", "content": "What does the GitHub Actions workflow 'QAI CI Pipeline' do?"}, {"role": "assistant", "content": "The workflow 'QAI CI Pipeline' is a CI/CD pipeline that:\n- Contains 3 job(s): validate, train, deploy\n- Uses 3 different GitHub Actions\n\nThis workflow is primarily focused on continuous integration checks."}], "source_workflow": "QAI CI Pipeline", "source_path": ".github/workflows/ci-pipeline.yml", "template": "overview", "hash": "2cba8f17f3a50cef"} +{"messages": [{"role": "user", "content": "What are the best practices demonstrated in the 'QAI CI Pipeline' workflow?"}, {"role": "assistant", "content": "The 'QAI CI Pipeline' workflow demonstrates several best practices:\n\n- Uses actions/checkout to ensure clean code access\n- Preserves build artifacts for debugging and deployment\n- Uses job dependencies to create a proper pipeline flow\n- Uses conditional job execution to optimize resource usage\n- Uses matrix strategy for testing across multiple configurations"}], "source_workflow": "QAI CI Pipeline", "source_path": ".github/workflows/ci-pipeline.yml", "template": "best_practices", "hash": "ff4be11d7d91c9f7"} +{"messages": [{"role": "user", "content": "How would I modify the 'QAI CI Pipeline' workflow to add a new step?"}, {"role": "assistant", "content": "To add a new step to the 'QAI CI Pipeline' workflow:\n\n1. Choose which job to modify (available: validate, train, deploy)\n2. Locate the `steps` section within that job\n3. Add a new step with:\n - `name`: A descriptive name for the step\n - `run`: Command(s) to execute, or\n - `uses`: An action to use (e.g., actions/checkout@v4)\n4. Optionally add conditions with `if:` to control when the step runs\n\nExample step structure:\n```yaml\n- name: My new step\n run: |\n echo \"Running my command\"\n python my_script.py\n```\n\nOr using an action:\n```yaml\n- name: Upload results\n uses: actions/upload-artifact@v4\n with:\n name: my-artifact\n path: results/\n```\n\nRemember to test your changes in a feature branch before merging to main."}], "source_workflow": "QAI CI Pipeline", "source_path": ".github/workflows/ci-pipeline.yml", "template": "modification", "hash": "b1c701c8d4ebb30b"} +{"messages": [{"role": "user", "content": "What are the best practices demonstrated in the 'Workflow Validation' workflow?"}, {"role": "assistant", "content": "The 'Workflow Validation' workflow demonstrates several best practices:\n\n- Uses actions/checkout to ensure clean code access\n- Uses job dependencies to create a proper pipeline flow"}], "source_workflow": "Workflow Validation", "source_path": ".github/workflows/workflow-validation.yml", "template": "best_practices", "hash": "e22a0cde6a82f7f0"} {"messages": [{"role": "user", "content": "What is the difference between 'run' and 'uses' in a workflow step?"}, {"role": "assistant", "content": "In GitHub Actions workflow steps:\n\n**run**: Executes shell commands directly\n```yaml\n- name: Install dependencies\n run: |\n npm install\n npm run build\n```\n- Runs arbitrary commands in the runner's shell\n- Can use multiple lines with `|` or `>`\n- Good for simple commands or scripts\n- Has access to environment variables\n\n**uses**: Invokes a reusable action\n```yaml\n- name: Checkout code\n uses: actions/checkout@v4\n with:\n fetch-depth: 0\n```\n- References a pre-built action from GitHub Marketplace or your repository\n- Actions are versioned (using @v4, @main, or commit SHA)\n- Can accept parameters via `with:`\n- Promotes code reuse and maintainability\n- Examples: actions/checkout, actions/setup-python, azure/login\n\n**When to use**:\n- Use `run` for simple commands and scripts\n- Use `uses` for complex operations, third-party integrations, or reusable logic"}], "source": "general_knowledge", "template": "concepts"} {"messages": [{"role": "user", "content": "What is the structure of a GitHub Actions workflow file?"}, {"role": "assistant", "content": "A GitHub Actions workflow file is a YAML file with the following main sections:\n\n1. **name**: Optional workflow name displayed in the Actions tab\n2. **on**: Defines triggers (push, pull_request, schedule, etc.)\n3. **jobs**: Contains one or more jobs to run\n - Each job has:\n - **runs-on**: Runner type (ubuntu-latest, windows-latest, etc.)\n - **steps**: Sequential actions or commands to execute\n - **needs**: Optional dependencies on other jobs\n4. **env**: Optional environment variables\n5. **permissions**: Optional permissions settings\n\nExample:\n```yaml\nname: CI\non: [push, pull_request]\njobs:\n test:\n runs-on: ubuntu-latest\n steps:\n - uses: actions/checkout@v4\n - run: npm test\n```"}], "source": "general_knowledge", "template": "structure"} -{"messages": [{"role": "user", "content": "What GitHub Actions are used in the 'Auto Validation' workflow?"}, {"role": "assistant", "content": "The workflow uses 3 different actions:\n\n- **./.github/actions/setup-python-env**: Performs ./.github/actions/setup-python-env functionality\n- **actions/checkout@v4**: Checks out the repository code\n- **actions/upload-artifact@v4**: Uploads build artifacts for later use"}], "source_workflow": "Auto Validation", "source_path": ".github/workflows/auto-validation.yml", "template": "actions", "hash": "fdf55377b27f9eed"} +{"messages": [{"role": "user", "content": "What GitHub Actions are used in the 'Workflow Validation' workflow?"}, {"role": "assistant", "content": "The workflow uses 3 different actions:\n\n- **./.github/actions/setup-python-env**: Performs ./.github/actions/setup-python-env functionality\n- **actions/checkout@v4**: Checks out the repository code\n- **actions/setup-python@v5**: Sets up a Python environment"}], "source_workflow": "Workflow Validation", "source_path": ".github/workflows/workflow-validation.yml", "template": "actions", "hash": "d2011230923a7766"} {"messages": [{"role": "user", "content": "What are the most common GitHub Actions triggers?"}, {"role": "assistant", "content": "The most common GitHub Actions triggers are:\n\n1. **push**: Triggers on code pushes to specified branches\n ```yaml\n on:\n push:\n branches: [main, dev]\n ```\n\n2. **pull_request**: Triggers on PR events (opened, synchronized, etc.)\n ```yaml\n on:\n pull_request:\n branches: [main]\n ```\n\n3. **schedule**: Triggers on a cron schedule\n ```yaml\n on:\n schedule:\n - cron: '0 2 * * *' # Daily at 2 AM UTC\n ```\n\n4. **workflow_dispatch**: Allows manual workflow runs\n ```yaml\n on:\n workflow_dispatch:\n inputs:\n environment:\n description: 'Environment to deploy to'\n required: true\n ```\n\n5. **release**: Triggers on release events\n ```yaml\n on:\n release:\n types: [published]\n ```"}], "source": "general_knowledge", "template": "triggers"} {"messages": [{"role": "user", "content": "How do I use secrets in GitHub Actions?"}, {"role": "assistant", "content": "To use secrets in GitHub Actions:\n\n1. **Add secrets**: Go to repository Settings > Secrets and variables > Actions\n2. **Click 'New repository secret'** and add your secret (e.g., API keys, passwords)\n3. **Reference in workflow**: Use `${{ secrets.SECRET_NAME }}` syntax\n\nExample:\n```yaml\nsteps:\n - name: Deploy\n env:\n API_KEY: ${{ secrets.API_KEY }}\n DATABASE_URL: ${{ secrets.DATABASE_URL }}\n run: |\n echo \"Deploying with credentials...\"\n ./deploy.sh\n```\n\n**Best practices**:\n- Never commit secrets to code\n- Use environment-specific secrets for dev/staging/prod\n- Secrets are masked in logs\n- Use GitHub's OIDC for cloud provider authentication when possible\n- Consider using environment protection rules for sensitive deployments"}], "source": "general_knowledge", "template": "secrets"} {"messages": [{"role": "user", "content": "How do I cache dependencies in GitHub Actions?"}, {"role": "assistant", "content": "Caching dependencies speeds up workflow runs by reusing previously downloaded packages:\n\n**Using actions/cache**:\n```yaml\nsteps:\n - uses: actions/checkout@v4\n \n - uses: actions/cache@v4\n with:\n path: ~/.npm\n key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}\n restore-keys: |\n ${{ runner.os }}-node-\n \n - run: npm install\n```\n\n**Language-specific setup actions** with built-in caching:\n```yaml\n# Python with pip cache\n- uses: actions/setup-python@v5\n with:\n python-version: '3.11'\n cache: 'pip'\n\n# Node.js with npm cache\n- uses: actions/setup-node@v4\n with:\n node-version: '20'\n cache: 'npm'\n```\n\n**Benefits**:\n- Reduces workflow time by 30-70%\n- Decreases network load\n- Cache expires after 7 days of no access\n- Maximum cache size: 10 GB per repository\n\n**Best practices**:\n- Use hash of lock files in cache key for version tracking\n- Include OS in key if caching OS-specific files\n- Use restore-keys for partial cache hits"}], "source": "general_knowledge", "template": "caching"} diff --git a/tests/test_quantum_provider.py b/tests/test_quantum_provider.py index eac8bc953..9b92d3b82 100644 --- a/tests/test_quantum_provider.py +++ b/tests/test_quantum_provider.py @@ -11,6 +11,8 @@ torch = pytest.importorskip("torch") +pytest.importorskip("torch", reason="torch is not installed") +import torch # noqa: E402 REPO_ROOT = Path(__file__).resolve().parents[1] CHAT_CLI_SRC = REPO_ROOT / "ai-projects" / "chat-cli" / "src" diff --git a/tests/test_sql_integration.py b/tests/test_sql_integration.py index f3f91ee89..aa3cf3a29 100644 --- a/tests/test_sql_integration.py +++ b/tests/test_sql_integration.py @@ -5,7 +5,7 @@ # Check if SQLAlchemy is available for these tests try: - # import sqlalchemy (unused) + import sqlalchemy as _sqlalchemy # noqa: F401 _sqlalchemy_available = True except ImportError: _sqlalchemy_available = False diff --git a/tests/test_ui_playwright.py b/tests/test_ui_playwright.py index 0ef6d6232..cb2bcc16f 100644 --- a/tests/test_ui_playwright.py +++ b/tests/test_ui_playwright.py @@ -9,6 +9,8 @@ from pathlib import Path +pytest.importorskip("playwright", reason="playwright is not installed") + REPO_ROOT = Path(__file__).resolve().parents[1] ARIA_WEB = REPO_ROOT / 'aria_web' SERVER_URL = 'http://127.0.0.1:8080' diff --git a/tests/test_vision_inference.py b/tests/test_vision_inference.py index 5d23c13e8..fc6aeec7b 100644 --- a/tests/test_vision_inference.py +++ b/tests/test_vision_inference.py @@ -3,6 +3,8 @@ Tests cover: """ # noqa: F401 +from __future__ import annotations + from typing import Any import importlib.util import base64 diff --git a/tests/test_web_app_security.py b/tests/test_web_app_security.py index ce172ecd0..9e179deeb 100644 --- a/tests/test_web_app_security.py +++ b/tests/test_web_app_security.py @@ -7,7 +7,9 @@ from typing import Any, Generator import pytest -from flask.testing import FlaskClient + +pytest.importorskip("flask", reason="flask is not installed") +from flask.testing import FlaskClient # noqa: E402 # Import the module under test REPO_ROOT = Path(__file__).resolve().parents[1]