Mismatch between preview builds and deployment checks

[alyssadai]

It seems we can have scenarios where the preview builds succeed but then the actual deployment fails.

In the case of a missing dependency in the cd workflow for example (as addressed in #69, our preview deploys may have picked up the requirements.txt implicitly (uhoh) and thus the previews looked fine, but then the actual deploy failed. Maybe we need to deploy via netlify for staging preview (now) and prod (future) so we are reviewing on the same. Should discuss

Originally posted by @surchs in #69 (review)

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!