It's pretty frustrating that Circle chokes on force pushes:

fatal: reference is not a tree: 1383c630553b2d1494218437ba741cec811c105d

maybe you shouldn't use force pushes then

it's perfectly normal in a wip branch (and much less so in master)

I tend to not like them for PR branches though.

it's very difficult to track what's happening when someone keeps force pushing their branch

and github supports squashing commits on merge anyway

force pushing can support far more than squashing... e.g. rebase -i with intentful editing of past commits anyway that's besides the point :)

:)

I notice Github actions works even less well with force pushes, CircleCI so far copes pretty well, but maybe not if you force push and some other step still has to fetch the branch. That's expected imo.

not sure, GH unlike gitlab keeps every git object (if that's the correct term) without any eventual GC

so I think the correct incantation will fetch 1383c630553b2d1494218437ba741cec811c105d wherever it is

ok, I've had some problems with this in the past, it could be improved now (but I like CircleCI much better :))