Except you might want different error handling for different error codes. For example, our validation errors return a JSON object as well but with 422.
So treating "get a response" and "get data from a response" separately works out well for us.
There's only a 6 hour different between the East coast and Hawaii. You can't entirely avoid a night shift, so you might as well have them all work from the same location.
If I was making edits more often, I might run into sync conflicts. But I mostly edit on my PC, then might make small edits to recipes while I'm working in the kitchen.
> Being able to hover a line, having the message of the commit which last changed it, and be able to say "ah ok, it was for this" is quite useful.
Honestly, this just sounds like we need better integrations with JIRA into dev tools. I'm not going to rewrite tickets in commits / PRs. That ticket has its own history, linked tickets, acceptance criteria, epics, related bug tickets, etc.
The first is solvable with a PR check. You can do whatever you want with the submodule on your branch, but if you want it to merge to `main`, then your changes to the submodule have to merged to its `main`.
We have a check that makes sure the referenced commits is on `main`, and not older than 10 PRs.