This. --force-with-lease is what --force should have been in the first place. Hopefully they will eventually make it so, and rename --force to something less accessible.
I would occasionally manage to start a bash shell without executing my profile, which means HISTFILESIZE is not set and bash would truncate my history on the first command I ran. zsh history may have a similar problem.
I think that's it! I've been wondering why Bash sometimes deletes most of my history for ages. My .bashrc sets up an EXIT trap that git-commits my history, so I just looked at the commits that remove lines and found that 7 out of 8 of those commits change the size of the history file to about 1000 lines. Since my history file contains timestamps, that matches the 500-command default of HISTSIZE, so the truncation mechanism you described seems to be what's happening.
A few days ago I actually made my history file append-only to prevent truncation.
> if a card is in the Done column, you can assume the
> code is in version control, deployed to production
> and checked to make sure it didn't explode on impact.
I guess you've never seen a team argue over "Definition of Done" for months.
> I guess you've never seen a team argue over "Definition of Done" for months.
Unfortunately, I have had that conversation plenty of times. The point is to have that conversation/argument once, make a decision on what it means for the team, and then move on.
Not quite the same, but you may own CA taxes on stock options if you earned them while living in CA even if you don't live there when you cash them in.
https://en.wikipedia.org/wiki/Chronology_of_Jesus