Rationalize all db command output text
Open
- Dominant language
- Ruby
- Stars
- 33
- Forks
- 55
- Avg merge
- 8d 7h
- Merged PRs (30d)
- 2
Description
Right now it all feels a bit noisy as well as inconsistent. Maybe pare it back a little and keep it simple. Perhaps avoid using the `measure` block for most of these, since the timing doesn't feel that important, and `measure`'s handling of failures results in confusing back-to-front text ordering (i.e. the specific error messages first, and then the summary of the command that failed _underneath_ it).
Contributor guide
Assessment
This issue has not been assessed yet.