Sorry for a long delay, just catching up on a ton of dev mail this morning.
FWIW, I agree that leaving feature/WIP branches in the main repository is bad
practice. The ease and flexibility of branching in Git leads to a strong
tendency towards proliferation of these things, and we really ought to apply
some discipline to the process to keep the repo history clean.
The detailed instructions on our Wiki re explicit re: use of forks for
contributions. All I see in the top-level "Contributing" page, however, is
this:
>>> Use a pull request to submit a code patch to the github mirror. Any new
>>> changes should be targeted at the "develop" branch.
Perhaps we should at least add a brief note here about forking?
Thanks,
Blake
On 6/11/20, 11:25 PM, "Jacob Barrett" <jabarr...@vmware.com> wrote:
> On Jun 11, 2020, at 8:41 PM, Owen Nichols <onich...@vmware.com> wrote:
>
> -1 for “banning”
:facepalm: Sorry, poor choice of words. How about “strongly discouraged”
because of the harm enumerated perviously.
>
> The Geode community has strong precedent for protecting developers’
freedom to choose what works best for them.
Not to the detriment of others in the community.
> Maybe check if your graphical git tool-of-choice allows a branch filter
regex, or consider git clone --single-branch?
Whether someone filters or not the issues enumerated exist even if hidden
away.
-Jake
