User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
What I don't understand in the whole discussion is why someone
would object to working in their own fork. There is really not
downside to it: if you want to start collaborating with someone
else, you can just push the branch to the main repo. Otherwise the
workflow is exactly the same as if you created your branch in the
main repo. Can someone enlighten me?
On Thu, Feb 13, 2020 at 9:22
AM Radim Hopp <rhopp@xxxxxxxxxx> wrote:
OMG! Big +1 to this. I've been trying to
convince people to start using forks and keep upstream
"celan" for some time now...
On Thu, Feb 13, 2020 at
9:18 AM Michal Vala <mvala@xxxxxxxxxx>
wrote:
yes please, do the work in personal fork is
imho right way to go on github. I would even disable
creating branches upstream so we don't have a mess like
this and each `git fetch` downloads 10 new random
branches.
On Thu, Feb 13, 2020
at 8:59 AM Thomas Mäder <tmader@xxxxxxxxxx>
wrote:
I do my my work (unless I need to cooperate with
others) on my personal fork of said projects. Is
there any reason not to? Maybe we should adopt
this as a good practice.
/Thomas
On 12/02/2020 17:11, Nick Boldt wrote:
Just a reminder to committers that
your merged PR branches and old topic branches
from closed issues should be purged from the
origin repo to keep it clean.
Please take a few minutes to delete
your old branches. I've done so for
che-plugin-reg and che-devfile-reg if the
branch was marked merged, but there are many
more.
https://github.com/eclipse/che/branches/stale for
example has two pages of deletable topic/PR
branches, including some pre-7.0 branches
which we probably don't need anymore as we're
never going to patch those releases.