CI/CD Pipeline Configuration Generator

You are a DevOps engineer who builds CI/CD pipelines. Create a CI/CD pipeline configuration for this project.

Project type: [WEB / API / LIBRARY / MOBILE]
Language/Framework: [TECH STACK]
CI/CD platform: [GITHUB ACTIONS / GITLAB CI / JENKINS / CIRCLECI]
Test types: [UNIT / INTEGRATION / E2E]
Deployment targets: [AWS / GCP / AZURE / VERCEL / OTHER]
Environments: [DEV / STAGING / PROD]
Approval requirements: [MANUAL / AUTOMATIC]

Provide:

**Pipeline Architecture**
```
[Code Push] → [Build] → [Test] → [Security Scan] → [Deploy Staging] → [Approval] → [Deploy Prod]
```

**GitHub Actions Workflow** (or platform-specific)
```yaml
name: CI/CD Pipeline

on:
  push:
    branches: [main, develop]
  pull_request:
    branches: [main]

jobs:
  lint:
    # Linting job
  
  test:
    # Unit and integration tests
  
  security:
    # Security scanning
  
  build:
    # Build artifacts
  
  deploy-staging:
    # Staging deployment
  
  deploy-production:
    # Production deployment with approval
```

**Environment Configuration**
- Secrets management
- Environment variables
- Environment-specific configs

**Quality Gates**
- Test coverage thresholds
- Linting rules
- Security scan requirements
- Performance benchmarks

**Deployment Strategies**
- Blue/green deployment
- Canary releases
- Feature flags
- Rollback procedures

**Notifications**
- Slack/Teams integration
- Failure alerts
- Deployment summaries

**Caching Strategy**
- Dependencies caching
- Build caching
- Docker layer caching

**Branch Protection**
- Required checks
- Review requirements
- Merge restrictions

**Monitoring & Observability**
- Deployment tracking
- Error monitoring integration
- Performance monitoring

**Cost Optimization**
- Parallel job configuration
- Resource right-sizing
- Conditional workflows

You are a DevOps engineer who builds CI/CD pipelines. Create a CI/CD pipeline configuration for this project.

Project type: [WEB / API / LIBRARY / MOBILE]
Language/Framework: [TECH STACK]
CI/CD platform: [GITHUB ACTIONS / GITLAB CI / JENKINS / CIRCLECI]
Test types: [UNIT / INTEGRATION / E2E]
Deployment targets: [AWS / GCP / AZURE / VERCEL / OTHER]
Environments: [DEV / STAGING / PROD]
Approval requirements: [MANUAL / AUTOMATIC]

Provide:

**Pipeline Architecture**
```
[Code Push] → [Build] → [Test] → [Security Scan] → [Deploy Staging] → [Approval] → [Deploy Prod]
```

**GitHub Actions Workflow** (or platform-specific)
```yaml
name: CI/CD Pipeline

on:
  push:
    branches: [main, develop]
  pull_request:
    branches: [main]

jobs:
  lint:
    # Linting job
  
  test:
    # Unit and integration tests
  
  security:
    # Security scanning
  
  build:
    # Build artifacts
  
  deploy-staging:
    # Staging deployment
  
  deploy-production:
    # Production deployment with approval
```

**Environment Configuration**
- Secrets management
- Environment variables
- Environment-specific configs

**Quality Gates**
- Test coverage thresholds
- Linting rules
- Security scan requirements
- Performance benchmarks

**Deployment Strategies**
- Blue/green deployment
- Canary releases
- Feature flags
- Rollback procedures

**Notifications**
- Slack/Teams integration
- Failure alerts
- Deployment summaries

**Caching Strategy**
- Dependencies caching
- Build caching
- Docker layer caching

**Branch Protection**
- Required checks
- Review requirements
- Merge restrictions

**Monitoring & Observability**
- Deployment tracking
- Error monitoring integration
- Performance monitoring

**Cost Optimization**
- Parallel job configuration
- Resource right-sizing
- Conditional workflows