Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Risk Estimate is no longer a WIP #20

Merged
merged 1 commit into from
Mar 18, 2024

Conversation

danielwheeler1987
Copy link
Contributor

Stakeholder Overview (learn more)

The Risk Estimate section of the PR Template is no longer a WIP. This has been in use for many months and has become part of our deployment process.

Risk Estimate (learn more)

This is change has NO risk at all.

  • Big/complex change
  • Big splash zone
  • High stakes if errors occur
  • Low confidence
  • ✅ Not hidden by feature flag
  • ✅ Negligible risk!

Changes

Updated Dependencies
  • None

Ticket

Monday issue

Screenshots

Notes

Recommended reading: Code Review guide

Optional Tasks

  • Include 🎩 Instructions
  • Update the readme (README.md)
  • Update the API or architecture docs (e.g. docs/api.md)
Library-Specific
  • Increment the changelog (CHANGELOG.md)
  • Increment the version number (lib/version.rb)
  • Release & Tag the version above in Github
Performance
  • Are there any new queries in your change set that might require new indexes?
  • Do any new queries require time-boxing to avoid table-scans when the data grows?

What GIF Best Describes This Pull Request?

@danielwheeler1987 danielwheeler1987 requested a review from a team as a code owner March 16, 2024 20:31
Copy link
Contributor

@paulslaby paulslaby left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙏

@danielwheeler1987 danielwheeler1987 merged commit af35db5 into master Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants