Skip to content

Instantly share code, notes, and snippets.

@MaxGabriel
Created December 18, 2019 13:34
Show Gist options
  • Save MaxGabriel/6e3aaed1cec07f28ebc6592b8909f0f6 to your computer and use it in GitHub Desktop.
Save MaxGabriel/6e3aaed1cec07f28ebc6592b8909f0f6 to your computer and use it in GitHub Desktop.
Mercury PR template

Testing Plan / How I Tested

  • Wrote a test
  • Tested locally (running SHA)
  • Tested on staging (running SHA)
  • Will test in production

Database

  • Indexes are added for new tables, or new data access patterns
  • Does my code make assumptions about the state of the database? If so, could these assumptions be enforced by the database or the database assumption checker?

Documentation

  • All new SQL tables are documented
  • New core data types are documented
  • Generally documented

Monitoring Plan

  • Does my code need to emit any data/logs to debug it later?
  • Could a recurring check be created to ensure continual correctness?

Informing the rest of the team

  • Consider the possible impacts to users
  • Inform people in #product
  • Notify @engineers about any changes in settings.yml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment