Objective

A repository at /home/interview/repo has a deployment workflow that deploys to both Staging and Production automatically on every push. Both jobs run in parallel with no ordering or approval.

Task

Modify the workflow at .github/workflows/deploy.yml to implement a gated deployment. The production job should only run after staging has completed successfully (using needs), and should be assigned to an environment named production (using environment).

File Path

• Workflow: /home/interview/repo/.github/workflows/deploy.yml

name: Deploy Service

on: push

jobs:
  staging:
    runs-on: ubuntu-latest
    steps:
      - run: echo "Deploying to Staging..."

  production:
    runs-on: ubuntu-latest
    needs: staging
    environment: production
    steps:
      - run: echo "Deploying to Production..."

Explanation

Step 1: Add Job Dependency

production:
  runs-on: ubuntu-latest
  needs: staging

needs: staging tells GitHub Actions that the production job cannot start until the staging job has completed successfully. Without this, both jobs run in parallel and production could deploy before staging is even done.

Step 2: Add Environment Protection

production:
  runs-on: ubuntu-latest
  needs: staging
  environment: production

environment: production assigns this job to a GitHub Environment named production. In a real GitHub setup, environments can have protection rules like required reviewers, wait timers, or branch restrictions. This means someone has to manually approve the production deployment before it runs.