BestPromptFinder

GitHub Actions CI Workflow for Tests and Lint

Quality, usefulness and confidence are AI evaluations out of 100 — not user ratings. Community results come from visitors' "worked / didn't work" votes below. How scoring works →

The prompt

Act as a CI/CD engineer. Write a GitHub Actions workflow for my repository. My project: - Language, version and package manager: [e.g. Python 3.13 with pip, Node 22 with pnpm] - Commands for install, lint, type check and tests: [COMMANDS] - When it should run: [on pull requests to main / on every push / nightly] - Services tests need: [e.g. Postgres, Redis, or none] - Secrets it needs (names only): [LIST or none] Give me: 1. A complete .github/workflows/ci.yml with: triggers, a job matrix if useful, dependency caching, separate steps for lint, type check and tests, and a test report or coverage upload if I want it: [YES / NO]. 2. Pinned versions for actions you use; mark any version you're unsure of [VERIFY]. 3. Minimal permissions for the workflow token. 4. A short explanation of each section and how to make the check required for merging. 5. The 3 most common reasons this kind of workflow fails, and how to debug them. Rules: never print secrets in logs; use the secrets context, not hard-coded values; keep it as short as possible while doing the job.

Why this prompt

• Hand-picked, editorially reviewed prompt
• Written for Claude, ChatGPT, Gemini

Source

Created by BestPromptFinder — editorial prompt, not user-generated. See our content & source policy.

Related Coding prompts