remote: Resolving deltas: 100% (3/3), completed with 3 local objects.
remote: fatal error in commit_refs
To github.com:acme/foo.git
! [remote rejected] HEAD -> acme/foo (failure)
error: failed to push some refs to 'github.com:acme/foo.git'
Almost. The sql package is just an abstract layer which requires a 3rd party module to provide the concretions. I guess the API is the same, but you still need a 3rd party lib :)
You can recover from a panic though, so if you are implementing something that may panic you should have some sensible defer/recover in there if you can't afford to have your process crash.
Call me old fashioned, but if you really want to see what something looks like on you just go to the store. Personally, I think buying clothes is not just about how they look on you but also how you feel in them. You can't replicate this with a digital solution (yet?).
Given most teams operate CI pipelines on their PRs/MRs, I like to make it a requirement to squash before merging. This means that only passing builds make it into the main branch.
The value of this cannot be underestimated, in my experience, as using things like “git bisect” mean you always have a working build.
This is a good place to get that kind of information