Objective

A repository at /home/interview/repo has a workflow with three jobs (lint, test, build) that all run in parallel with no dependencies. The build job can execute even if lint or test fails.

Task

Update the workflow at .github/workflows/pipeline.yml to enforce a strict execution sequence: lint → test → build. The test job should depend on lint, and build should depend on test. If any job fails, the subsequent jobs should be skipped.

File Path

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

name: Production Pipeline

on: push

jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
      - run: echo "Linting code..."

  test:
    runs-on: ubuntu-latest
    needs: lint
    steps:
      - run: echo "Running tests..."

  build:
    runs-on: ubuntu-latest
    needs: test
    steps:
      - run: echo "Building artifact..."

Explanation

Step 1: Test Depends on Lint

test:
  runs-on: ubuntu-latest
  needs: lint

needs: lint means the test job won't start until lint has completed successfully. If lint fails, test is skipped entirely.

Step 2: Build Depends on Test

build:
  runs-on: ubuntu-latest
  needs: test

needs: test means build waits for test. Since test already depends on lint, this creates a chain: lint → test → build. If lint fails, test is skipped, which means build is also skipped. The entire chain stops at the first failure.