GitHub Environments: deployment history and audit trail

When something breaks in production, it is difficult to know what was deployed when, by whom, and from which commit. The audit trail is scattered across Slack, git log, and CI run history.

Use GitHub Environments to get automatic deployment history in the GitHub UI:

jobs:
  deploy:
    runs-on: ubuntu-latest
    environment:
      name: production
      url: https://myapp.com
    steps:
      - run: ./deploy.sh

Every run creates a deployment record at github.com/org/repo/deployments showing:

• Which commit was deployed
• Who triggered it
• When it started and ended
• Whether it succeeded
• A direct link to the deployed URL

Use the GitHub API to query deployment history:

gh api /repos/{owner}/{repo}/deployments \
  --jq '.[] | {sha: .sha, created_at: .created_at, creator: .creator.login}'

Centralised deployment history in GitHub means any engineer can answer 'what is deployed right now' in seconds, without access to your CI system or cloud console.