circleci

rm -rf /home/circleci/.gitconfig
vemv 2021-07-01T09:02:26.016900Z

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

fatal: reference is not a tree: 1383c630553b2d1494218437ba741cec811c105d
often I want the old build to keep running even if another build superseded it

borkdude 2021-07-01T09:03:19.018Z

maybe you shouldn't use force pushes then

vemv 2021-07-01T09:04:05.019Z

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

borkdude 2021-07-01T09:04:23.019300Z

I tend to not like them for PR branches though.

borkdude 2021-07-01T09:04:37.019600Z

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

borkdude 2021-07-01T09:04:59.019900Z

and github supports squashing commits on merge anyway

vemv 2021-07-01T09:06:28.021Z

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

borkdude 2021-07-01T09:07:15.021200Z

:)

borkdude 2021-07-01T09:08:34.021900Z

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.

vemv 2021-07-01T09:09:31.022700Z

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

vemv 2021-07-01T09:09:51.023200Z

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

borkdude 2021-07-01T09:10:37.023600Z

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

👍 1