▸case-01 We want to set up automated deployments to our Kubernetes cluster using GitHub Actions after changes land on the main branch. Please write out the full GitHub Actions workflow YAML script that handles cluster authentication and applies our manifest files, including a step-by-step verification guide. | fail→fail | 23,258 | 13,172 | -43% | 1 | 1 | 0% | 3,777 | 2,862 | -24% | 0 | 0 | — |
▸case-02 Write a GitLab CI/CD `.gitlab-ci.yml` pipeline configuration file to build a Node.js application and run Jest unit tests on merge requests. | pass→pass | 16,833 | 11,648 | -31% | 1 | 1 | 0% | 2,411 | 2,442 | +1% | 0 | 0 | — |
▸case-03 Create a Jenkinsfile script using Declarative Pipeline syntax to execute a Maven build and run SonarQube static code analysis. | pass→pass | 13,287 | 10,103 | -24% | 1 | 1 | 0% | 2,221 | 2,125 | -4% | 0 | 0 | — |
▸case-04 Write a local Bash shell script to build a local Docker container image, tag it with git commit hash, and deploy it to a local minikube cluster using kubectl. | pass→pass | 15,832 | 16,640 | +5% | 1 | 1 | 0% | 3,160 | 2,898 | -8% | 0 | 0 | — |
▸case-05 We need a GitHub Actions job that builds a Docker image for our application and pushes it to GitHub Packages at ghcr.io. We currently use standard docker build commands without buildx or layer caching, which makes CI builds take 15 minutes. Produce a workflow file for this build step. | pass→pass | 14,699 | 15,445 | +5% | 1 | 1 | 0% | 2,389 | 2,716 | +14% | 0 | 0 | — |
▸case-06 We are creating a GitHub Actions deployment workflow for AWS EKS. A junior developer suggested storing long-lived AWS secret keys in repository secrets AWS_SECRET_ACCESS_KEY. Provide the recommended production workflow YAML configuration. | pass→pass | 17,218 | 16,856 | -2% | 1 | 1 | 0% | 2,689 | 2,960 | +10% | 0 | 0 | — |
▸case-07 We need a GitHub Actions workflow to run our test suite across Python versions 3.9, 3.10, and 3.11 on both ubuntu-latest and windows-latest. We want all matrix combinations to finish running even if one specific combination fails. Draft the workflow strategy section. | pass→pass | 3,979 | 8,397 | +111% | 1 | 1 | 0% | 692 | 1,899 | +174% | 0 | 0 | — |
▸case-08 Create a GitHub Actions step for docker metadata tags when pushing images to Docker Hub on release tags and main branch pushes. Ensure tags follow semantic versioning and commit SHA standards rather than defaulting only to latest. | pass→pass | 15,200 | 9,295 | -39% | 1 | 1 | 0% | 2,400 | 2,264 | -6% | 0 | 0 | — |
▸case-09 We want to add container vulnerability scanning to our CI pipeline before pushing Docker images. The team requested that security scan results appear directly in GitHub Security tab. Write the workflow job for container scanning. | pass→pass | 16,276 | 10,036 | -38% | 1 | 1 | 0% | 2,853 | 2,087 | -27% | 0 | 0 | — |
▸case-10 In our Kubernetes deployment workflow step, after executing kubectl apply -f k8s/, the pipeline immediately marks the step as successful even if the new pods crash. Provide the step configuration to ensure deployment health is verified. | pass→pass | 14,080 | 8,658 | -39% | 1 | 1 | 0% | 2,523 | 1,864 | -26% | 0 | 0 | — |
▸case-11 We have multiple microservices repositories that need to run identical build, test, and security scan steps. We want a centralized workflow definition in an infrastructure repository that other repositories can call. Draft the caller and called workflow header setup. | pass→pass | 13,823 | 9,286 | -33% | 1 | 1 | 0% | 2,095 | 2,003 | -4% | 0 | 0 | — |
▸case-12 Our Node.js CI test workflow executes npm ci on every pull request, taking 8 minutes because it downloads node_modules from scratch each time. Write a GitHub Actions job step configuration that properly caches dependencies. | pass→pass | 11,026 | 10,207 | -7% | 1 | 1 | 0% | 1,509 | 2,167 | +44% | 0 | 0 | — |
▸case-13 We run CI testing across Python 3.8, 3.9, 3.10 on ubuntu-latest, macos-latest, and windows-latest. However, Python 3.8 is not supported on macos-latest in our project, so that exact combination must be skipped. Write the matrix strategy block. | pass→pass | 7,343 | 6,611 | -10% | 1 | 1 | 0% | 1,030 | 1,526 | +48% | 0 | 0 | — |
▸case-14 Design a GitHub Actions workflow for static application security testing using CodeQL that runs automatically on weekly schedules and on pull requests targeting the main branch. | pass→pass | 13,081 | 14,384 | +10% | 1 | 1 | 0% | 2,419 | 2,785 | +15% | 0 | 0 | — |
▸case-15 A team member wrote a deployment workflow that sets top-level permissions to permissions: write-all. Write the corrected GitHub Actions permissions block following the principle of least privilege for a job that reads repository contents and writes security SARIF reports. | pass→pass | 2,956 | 7,297 | +147% | 1 | 1 | 0% | 489 | 1,503 | +207% | 0 | 0 | — |
▸case-16 We deploy our web application to Kubernetes using Helm charts stored in our repository. Write the GitHub Actions workflow steps to set up Helm CLI and run lint validation before deploying. | pass→pass | 9,822 | 10,580 | +8% | 1 | 1 | 0% | 1,801 | 1,863 | +3% | 0 | 0 | — |
▸case-17 When developers push multiple commits in rapid succession to a pull request, multiple concurrent workflow runs get queued up, wasting CI minutes. Write the workflow configuration to automatically cancel pending or in-progress runs for older commits on the same branch. | pass→pass | 7,726 | 6,640 | -14% | 1 | 1 | 0% | 1,517 | 1,564 | +3% | 0 | 0 | — |
▸case-18 Where in the project resources can detailed step-by-step example playbooks for building complex multi-architecture Docker images and deploying via Helm be found when additional guidance is required? | fail→pass | 15,065 | 1,724 | -89% | 1 | 1 | 0% | 1,947 | 625 | -68% | 0 | 0 | — |
▸case-19 Our repository contains both documentation markdown files and application source code under src/. CI test runs trigger every time someone edits README.md. Modify the GitHub Actions on: trigger settings so tests only execute when files under src/ or package.json are modified. | pass→pass | 6,854 | 6,601 | -4% | 1 | 1 | 0% | 1,226 | 1,410 | +15% | 0 | 0 | — |
▸case-20 We have a monorepo with services/api and services/web. We want a GitHub Actions test workflow that runs Go tests specifically when changes occur in services/api/**. Draft the workflow configuration. | pass→pass | 12,988 | 10,785 | -17% | 1 | 1 | 0% | 2,023 | 2,337 | +16% | 0 | 0 | — |
▸case-21 We have a two-job GitHub Actions workflow: job 1 builds a frontend single-page app into dist/, and job 2 deploys those built static assets to an S3 bucket. Write the workflow steps that share the dist/ directory between job 1 and job 2. | pass→pass | 9,493 | 7,330 | -23% | 1 | 1 | 0% | 1,598 | 1,952 | +22% | 0 | 0 | — |
▸case-22 We want our GitHub Actions deployment to production to require manual approval in the GitHub UI and use secret variables specific to the production deployment target. How is this configured in the deployment workflow job? | fail→fail | 9,295 | 7,993 | -14% | 1 | 1 | 0% | 1,454 | 1,868 | +28% | 0 | 0 | — |