▸case-01 I'm writing a GitHub Actions workflow step using `actions/github-script` to summarize our test suite results in `$GITHUB_STEP_SUMMARY`. Could you write the script that renders the overall test execution status, pass/fail metrics, and long diagnostic output from failed test cases? | fail→pass | 14,378 | 11,360 | -21% | 1 | 1 | 0% | 2,954 | 2,470 | -16% | 0 | 0 | — |
▸case-02 Please write Markdown content to be pushed to `$GITHUB_STEP_SUMMARY` after our container security scanning job finishes. The report should highlight vulnerability severity levels, affected packages, suggested remedies, and the raw scan logs. | fail→pass | 12,151 | 12,479 | +3% | 1 | 1 | 0% | 2,394 | 2,796 | +17% | 0 | 0 | — |
▸case-03 I need to generate a GitHub Actions step summary for a pull request code review workflow. Can you provide the markdown template that summarizes static analysis findings, impacted file paths, and build logs for the job run? | fail→pass | 16,601 | 9,411 | -43% | 1 | 1 | 0% | 2,921 | 1,843 | -37% | 0 | 0 | — |
▸case-04 I want to log error and warning annotations directly to standard output during a GitHub Actions runner execution using workflow commands so they appear inline on PR code diffs. How should I format these console outputs? | pass→pass | 9,474 | 8,087 | -15% | 1 | 1 | 0% | 1,638 | 1,600 | -2% | 0 | 0 | — |
▸case-05 We are creating a PR comment via the GitHub REST API (`octokit.rest.issues.createComment`) from a GitHub Actions workflow to post deployment previews. What markdown should we send in the body field? | pass→pass | 9,697 | 7,490 | -23% | 1 | 1 | 0% | 1,788 | 1,478 | -17% | 0 | 0 | — |
▸case-06 We are writing a script that generates release notes for a GitHub Release tag based on merged PR titles and commit history. Provide a markdown template for the release notes file. | pass→fail | 9,921 | 5,215 | -47% | 1 | 1 | 0% | 1,929 | 1,269 | -34% | 0 | 0 | — |
▸case-07 Write an `actions/github-script` snippet that generates a step summary for a Kubernetes deployment job in GitHub Actions. The job deployed service `auth-api` to cluster `prod-us-east-1` and generated multi-page roll-out event logs. Make the headings prominent so engineers notice them. | fail→pass | 12,037 | 10,496 | -13% | 1 | 1 | 0% | 2,207 | 2,459 | +11% | 0 | 0 | — |
▸case-08 I need a markdown report appended to `$GITHUB_STEP_SUMMARY` after an ESLint step fails in GitHub Actions. It should display total error counts, affected rule names, and the full stack trace outputs. Use eye-catching icons in the titles so developers pay attention. | pass→pass | 17,958 | 8,264 | -54% | 1 | 1 | 0% | 3,456 | 1,663 | -52% | 0 | 0 | — |
▸case-09 Provide a markdown template to append to `$GITHUB_STEP_SUMMARY` for a Terraform plan execution in GitHub Actions. Show resource counts (to add, change, destroy) at the top, followed by the complete multi-hundred line plan output. I want top-level H1 tags for major sections. | fail→pass | 10,960 | 7,919 | -28% | 1 | 1 | 0% | 2,209 | 1,846 | -16% | 0 | 0 | — |
▸case-10 Write a summary markdown script for `$GITHUB_STEP_SUMMARY` after a JaCoCo code coverage job runs in GitHub Actions. Highlight overall line coverage percentage, uncovered class paths, and detailed line-by-line coverage breakdown tables. | pass→pass | 18,520 | 13,412 | -28% | 1 | 1 | 0% | 3,865 | 2,983 | -23% | 0 | 0 | — |
▸case-11 Create a markdown snippet for `$GITHUB_STEP_SUMMARY` documenting a Flyway database migration step in GitHub Actions. Include applied migration IDs, execution duration, and full SQL execution logs. | pass→pass | 8,459 | 7,266 | -14% | 1 | 1 | 0% | 1,774 | 1,562 | -12% | 0 | 0 | — |
▸case-12 Construct an `actions/github-script` block that writes a step summary for a Cypress test runner step. Include pass/fail summary counters, failed test spec names, and browser console output logs. | fail→pass | 14,425 | 11,070 | -23% | 1 | 1 | 0% | 2,806 | 2,692 | -4% | 0 | 0 | — |
▸case-13 Write a step summary markdown generator for an `npm audit` step in GitHub Actions. Display vulnerability count breakdowns first, followed by package names, severity ratings, and verbose package dependency trees. | pass→pass | 20,121 | 11,526 | -43% | 1 | 1 | 0% | 3,820 | 2,814 | -26% | 0 | 0 | — |
▸case-14 Create a GitHub Actions step summary template for a Docker image build step. Show the final image digest, tag names, build time, and full layer build stdout logs. Add decorative status emojis to every heading line. | fail→pass | 15,367 | 7,160 | -53% | 1 | 1 | 0% | 2,994 | 1,766 | -41% | 0 | 0 | — |
▸case-15 Generate a markdown document for `$GITHUB_STEP_SUMMARY` summarizing a Semgrep SAST scan. Highlight critical finding totals, rule IDs, file locations, and suggested remediation diff snippets. | fail→pass | 11,904 | 9,122 | -23% | 1 | 1 | 0% | 2,571 | 2,162 | -16% | 0 | 0 | — |
▸case-16 Provide markdown content for `$GITHUB_STEP_SUMMARY` reporting k6 load test results in GitHub Actions. Render key metrics (p95 latency, RPS, error rate) at the top and raw JSON test result payloads at the bottom. | pass→pass | 10,918 | 7,405 | -32% | 1 | 1 | 0% | 2,131 | 1,850 | -13% | 0 | 0 | — |
▸case-17 Write markdown content for `$GITHUB_STEP_SUMMARY` after an AWS Prowler compliance scan finishes in GitHub Actions. Show pass/fail compliance checks, failed control IDs, and verbose raw compliance report payloads. | pass→pass | 15,654 | 12,606 | -19% | 1 | 1 | 0% | 2,795 | 2,846 | +2% | 0 | 0 | — |
▸case-18 Write a GitHub Actions step summary markdown template for a `helm template` dry-run verification job. Include release name, target namespace, chart version, and generated multi-document Kubernetes manifest YAML. | fail→pass | 10,781 | 9,899 | -8% | 1 | 1 | 0% | 2,070 | 2,333 | +13% | 0 | 0 | — |
▸case-19 Construct a step summary template for a Python linting and formatting step in GitHub Actions. Display total violation count, list of affected python files, and full diff outputs. | fail→pass | 15,661 | 8,943 | -43% | 1 | 1 | 0% | 2,883 | 1,961 | -32% | 0 | 0 | — |
▸case-20 Using `actions/github-script`, write code that generates `$GITHUB_STEP_SUMMARY` for a Java Maven build step. Report build status, compilation warning counts, and full build console logs. | fail→pass | 17,559 | 7,117 | -59% | 1 | 1 | 0% | 2,971 | 1,531 | -48% | 0 | 0 | — |
▸case-21 Generate a markdown summary template for `$GITHUB_STEP_SUMMARY` following an Android APK build and signing workflow step in GitHub Actions. Include APK file size, SHA256 checksums, signing key alias, and full bundletool output. | pass→pass | 8,927 | 9,094 | +2% | 1 | 1 | 0% | 1,709 | 1,933 | +13% | 0 | 0 | — |
▸case-22 Create a markdown template for `$GITHUB_STEP_SUMMARY` to report results of an Ansible playbook execution in GitHub Actions. Show play stats (ok, changed, failed), affected host IP addresses, and verbose task execution output. | fail→pass | 16,562 | 8,634 | -48% | 1 | 1 | 0% | 2,959 | 1,969 | -33% | 0 | 0 | — |