Configure a CI/CD Pipeline with GitHub Actions
Configure a professional CI/CD pipeline with GitHub Actions covering tests, security, Docker build, and multi-environment deployment.
Paste in your AI
Paste this prompt in ChatGPT, Claude or Gemini and customize the variables in brackets.
Tu es un expert DevOps spécialisé dans l'automatisation des pipelines CI/CD avec GitHub Actions. Je dois mettre en place un pipeline complet pour mon projet. **Informations sur le projet :** - Type : [EX: API Node.js, application React, microservice Python] - Environnements cibles : [EX: staging sur Render, production sur AWS ECS] - Registry Docker : [EX: GitHub Container Registry, DockerHub, AWS ECR] - Base de données : [EX: PostgreSQL, migration avec Prisma] - Tests : [EX: Jest pour unitaires, Playwright pour E2E] **Exigences du pipeline :** - Branches : [EX: feature/* → staging, main → production] - Secrets nécessaires : [LISTER_LES_NOMS_DE_SECRETS_SANS_VALEURS] - Notifications : [EX: Slack, email sur échec] Crée les fichiers GitHub Actions complets pour : 1. **Workflow CI** (.github/workflows/ci.yml) : lint, tests unitaires, tests d'intégration, analyse de sécurité (Trivy, SAST), rapport de couverture de code. 2. **Workflow CD** (.github/workflows/cd.yml) : build et push de l'image Docker, déploiement sur staging automatique, déploiement en production avec validation manuelle. 3. **Workflow de release** : génération automatique du changelog et création de releases GitHub. Pour chaque workflow, explique le rôle de chaque job et step, et indique les optimisations de cache utilisées pour accélérer les builds.
Why this prompt works
<p>This prompt is designed to produce immediately usable GitHub Actions workflows covering the three essential pipeline types: continuous integration (CI), continuous deployment (CD), and release management. The separation into three distinct files follows modularity best practices.</p><p>Including security analysis (Trivy for container vulnerabilities, SAST for code) from the CI phase is crucial as it detects issues earliest in the development cycle, where fixing them costs the least.</p><p>Requesting explanations about cache optimizations transforms this prompt into a learning tool: understanding why we cache node_modules or Docker layers allows developers to reproduce and adapt these optimizations in other contexts.</p>
Use Cases
Expected Output
Three complete GitHub Actions YAML files for CI, CD, and release, with explanations of each step and cache optimizations.
Learn more
Check the full skill on Prompt Guide to master this technique from A to Z.
View on Prompt Guide📬 Get new prompts every week
Join our newsletter and never miss a prompt.
Similar Prompts
Debug a Production Error
Quickly analyze a production error with a structured Root Cause Analysis approach and an immediate action plan.
Refactor Legacy Code Step by Step
This prompt guides AI to analyze legacy code and produce a structured refactoring plan with diagnosis, prioritization, tests, and modernized code.
Create a CLI Tool with Node.js
Create a professional Node.js CLI tool with Commander.js, Inquirer, visual feedback, and npm publishing.
Optimize Your SQL Queries and Boost Performance
A complete prompt to analyze, diagnose, and optimize your SQL queries with indexing and rewriting recommendations adapted to your database engine.