Implement CI/CD foundation with GitHub Actions workflows

[Copilot]

Establishes automated CI/CD pipeline for ResumeSpy backend with environment-aware deployment stubs and comprehensive operational documentation.

Workflows

CI (.github/workflows/ci.yml)

• Validates PRs to main and release/** branches
• Runs restore → build → test pipeline
• Cancels in-progress runs on new commits

CD (.github/workflows/cd.yml)

• Deploys to DEV on merge to main
• Deploys to PROD on push to release/**
• Includes deployment stubs with implementation guidance

environment: 
  name: ${{ github.ref == 'refs/heads/main' && 'DEV' || 'PROD' }}

Documentation

ENVIRONMENTS.md (372 lines)

• Environment matrix (Local/DEV/PROD)
• Secrets configuration per environment
• Database, CORS, OAuth setup
• Security best practices

DEPLOYMENT.md (482 lines)

• Platform-specific guides: Azure, Railway, Docker+VPS, AWS
• Database migration strategies
• Secrets configuration workflows

CONTRIBUTING.md (525 lines)

• Development workflow and branch conventions
• Conventional Commits format
• Code standards aligned with Clean Architecture

Configuration

• .env.example: Environment variable template covering database, JWT, OAuth
• .gitignore: Excludes /publish and *.env files
• README.md: Added CI/CD badges, pipeline diagrams, environment matrix, project structure

Deployment Stubs

Current CD workflow publishes artifacts but uses deployment stubs:

- name: Deploy to DEV
  if: github.ref == 'refs/heads/main'
  run: |
    echo "⚠️  DEPLOYMENT STUB - This is a placeholder"
    echo "To implement: configure target, set secrets, use deployment action"

Follow docs/DEPLOYMENT.md to implement actual deployment. Intentionally minimal foundation - monitoring, rollback, containerization can be added incrementally.

Original prompt

CI/CD Foundation Implementation

Overview

Implement a clean, minimal, and extensible CI/CD foundation for the ResumeSpy backend API using GitHub Actions.

Context

This is a backend .NET 9.0 Web API repository that is part of a frontend-backend separated system. The repository needs automated continuous integration and deployment pipelines to:

• Validate PRs before merge
• Deploy to DEV on merge to main
• Deploy to PROD on push to release branches

Implementation Requirements

1. Create CI Workflow: .github/workflows/ci.yml

name: CI - Pull Request Validation

# Trigger this workflow on pull requests targeting main or release branches
on:
  pull_request:
    branches: 
      - main
      - 'release/**'

# Cancel in-progress CI runs for the same PR when new commits are pushed
concurrency: 
  group: ci-${{ github.ref }}
  cancel-in-progress: true

jobs:
  build-and-test:
    name: Build and Test
    runs-on: ubuntu-latest
    
    steps:
      # Step 1: Check out the code
      - name: Checkout code
        uses: actions/checkout@v4
      
      # Step 2: Set up .NET 9.0 SDK
      - name: Setup .NET 9.0
        uses: actions/setup-dotnet@v4
        with:
          dotnet-version: '9.0.x'
      
      # Step 3: Restore dependencies
      - name: Restore dependencies
        run: dotnet restore ResumeSpy.sln
      
      # Step 4: Build the solution in Release mode
      - name: Build solution
        run: dotnet build ResumeSpy.sln --configuration Release --no-restore
      
      # Step 5: Run tests (if any exist)
      # This will succeed even if no tests are found, but will fail if tests exist and fail
      - name: Run tests
        run: dotnet test ResumeSpy.sln --configuration Release --no-build --verbosity normal
      
      # Step 6: Report status
      - name: CI Summary
        if: success()
        run: |
          echo "✅ CI passed successfully"
          echo "- Build completed"
          echo "- All tests passed (or no tests found)"
          echo "- Code is ready to merge"

2. Create CD Workflow: .github/workflows/cd.yml

name: CD - Continuous Deployment

# Trigger this workflow on pushes to main (DEV) or release branches (PROD)
on:
  push:
    branches: 
      - main
      - 'release/**'

# Prevent concurrent deployments to the same environment
concurrency: 
  group: deploy-${{ github.ref }}
  cancel-in-progress: false  # Don't cancel deployments, queue them instead

jobs:
  build-and-deploy:
    name: Build and Deploy
    runs-on: ubuntu-latest
    
    # Set environment name based on branch
    environment: 
      name: ${{ github.ref == 'refs/heads/main' && 'DEV' || 'PROD' }}
    
    steps:
      # Step 1: Check out the code
      - name: Checkout code
        uses: actions/checkout@v4
      
      # Step 2: Set up .NET 9.0 SDK
      - name: Setup .NET 9.0
        uses: actions/setup-dotnet@v4
        with:
          dotnet-version: '9.0.x'
      
      # Step 3: Restore dependencies
      - name: Restore dependencies
        run: dotnet restore ResumeSpy.sln
      
      # Step 4: Build the solution in Release mode
      - name: Build solution
        run: dotnet build ResumeSpy.sln --configuration Release --no-restore
      
      # Step 5: Run tests
      - name: Run tests
        run: dotnet test ResumeSpy.sln --configuration Release --no-build --verbosity normal
      
      # Step 6: Publish application (prepare deployment artifacts)
      - name: Publish application
        run: |
          dotnet publish ResumeSpy.UI/ResumeSpy.UI.csproj \
            --configuration Release \
            --no-build \
            --output ./publish
      
      # Step 7: Deploy to DEV (runs only on main branch)
      - name: Deploy to DEV
        if: github.ref == 'refs/heads/main'
        run: |
          echo "🚀 Deploying to DEV environment..."
          echo ""
          echo "Branch: ${{ github.ref_name }}"
          echo "Commit: ${{ github.sha }}"
          echo "Triggered by: ${{ github.actor }}"
          echo ""
          echo "📦 Deployment artifacts ready in ./publish"
          echo ""
          echo "⚠️  DEPLOYMENT STUB - This is a placeholder implementation"
          echo ""
          echo "To implement actual deployment, you would:"
          echo "  1. Configure deployment target (Azure, AWS, Railway, Fly.io, etc.)"
          echo "  2. Set up secrets in GitHub:"
          echo "     - DEV_DEPLOY_TOKEN (authentication)"
          echo "     - DEV_CONNECTION_STRING (database)"
          echo "     - DEV_JWT_SIGNING_KEY (app secret)"
          echo "  3. Use deployment action or CLI tool"
          echo ""
          echo "Example deployment commands:"
          echo "  # Azure App Service:"
          echo "  # az webapp deploy --resource-group <rg> --name <app> --src-path ./publish"
          echo ""
          echo "  # Railway:"
          echo "  # railway up --service backend --environment dev"
          echo ""
          echo "  # Docke...

</details>



<!-- START COPILOT CODING AGENT SUFFIX -->

*This pull request was created from Copilot chat.*
>

<!-- START COPILOT CODING AGENT TIPS -->
---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our [2 minute survey](https://gh.io/copilot-coding-agent-survey).