I've just deleted branch

to-be-deleted-main

from the lakeFS repository, which used to be called "`main`". Nobody's ever used it, and it contained some filename case issues. The branch tip was

8ff9846ab6e9aacdea56606ff9dde135c42e4f83

. I am purposefully not generating a tag there. To be clear: the lakeFS trunk is named "`master`". WHY? This branch was an aborted attempt to rename

master

(the lakeFS repo was opened back when this horribly incorrect name was the default). This particular renaming was broken because of some uppercase/lowercase renamings. And those cause issues on a case-insensitive filesystem -- which MacOS helpfully provides by default. So it used to be that after

git checkout main

on a macOS box you'd need to seek expert help to recover your local repo on that box... WHY does trunk remain

master

? It is an incorrect name with horrible connotations (and not one used historically). However renaming trunk requires a simultaneous (not concurrent!) change: all developers must rename

master

->

main

on the same commit, all actions must change to accept the new name, and other unknown dependencies will break. (I would appreciate pointers to articles from any open-source projects about good practices for doing and testing this!)

Thanks a ton @Ariel Shaqed (Scolnicov) for this detailed explanation! Yes, seems like for very dynamic and extensive projects like lakeFS it's not that easy to just rename the trunk / mainline branch w/o braking the project in a major way. Hence, let's live with it for now.