denoland / denoland/deploy_feedback
`<app_name>.deno.dev` should not point at the latest commit if it fails to startup
Open
- Dominant language
- No language data
- Stars
- 79
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
I just pushed a commit which ran locally but ended up calling a missing file system API and crashing on the server. It seems like the non-hashed commit cname should only point to the latest commit after a health check of sorts.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.