-1 for “banning” The Geode community has strong precedent for protecting developers’ freedom to choose what works best for them.
Maybe check if your graphical git tool-of-choice allows a branch filter regex, or consider git clone --single-branch? -Owen On June 11, 2020 at 5:23:20 PM PDT, Jinmei Liao <jil...@vmware.com> wrote: +1 for ban the use of geode repo for feature branches. Less clutter is better. ________________________________ From: Jacob Barrett <jbarr...@pivotal.io> Sent: Tuesday, June 2, 2020 3:42 PM To: dev@geode.apache.org <dev@geode.apache.org> Subject: [DISCUSSION] Stop using the Geode Repository for Feature/WIP Branches I know this has been brought up multiple times without resolution. I want us resolve to ban the use of Geode repository for work in progress, feature branches, or any other branches that are not release or support branches. There is no reason given the nature of GitHub why you can’t fork the repository to contribute. * Work done on these branches results in the ASF bots updating the associated JIRAs and email blasting all of us with your work. * People don’t clean up these branches, which leads to a mess of branches on everyones clones and in the UI. * All your intermediate commits get synced to the repo, which bloats the repo for everyone else. Even your commits you rebase over and force push are left in the repo. When you delete your branch these commits are not removed. There is no way for us to prune unreferenced commits. Nobody else needs your commits outside of what was merged to a production branch. If anyone has a use case for working directly from Geode repo that can’t work from a fork please post it here so we can resolve. Thanks, Jake
