[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [che-dev] Stale branches in che repos :: ACTION REQUIRED :: please take out your trash :D
|
I agree with Anatolii on this one: my intent in bringing this up
was never to disable branches, but only to change our standard
operating procedure.
/Thomas
On 24/02/2020 08:17, Anatolii Bazko
wrote:
Hello.
Sorry, but I am strongly against that.
It will bring complications when several developers work on the
same issue.
Ok so it looks like we need to change our
github repositories configurations. Sun do you want to take
the action item?
Hello, so here is the result of the survey:
Sorry, I had not finished my "for
example", but hope you've got the idea ;)
I don't want to force you to do
anything, I want to understand why you
work that way. Maybe there is a cost to
working in forks which I'm not seeing.
It's an honest question.
If we are talking about me: at some
point, I've switched my preferences to work
with forks.
However, I respect the rights of other
contributors to work in a way that way want
to work.
Without asking why if we don't have a
strong technical reason for that.
Let me put this story from a different
angle.
Is there a reason to keep branches of merged
or closed PRs?
That really looks like garbage. Don't you
think so?
/Thomas
On 18/02/2020 09:46, Sergii
Kabashniuk wrote:
What I didn't understand
is why do you forcing someone to do
things in the way you like to do
without strong technical reasons?
Why we are ignoring diversity and
pushing everybody to work in the way
how the mainstream is doing?
Is there a technical reason why
we should not allow some
contributors to collaborate in the
way how they used to do that for
years?
I proposed to move this conversation
in a less strict tone.
1. Propose the recommended way to do
the contribution.
2. Propose the recommended way for
branch names.
3. Encourage people to clean up
after the work has been done.
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?
/Thomas
On 17/02/2020 17:19, Sun Tan
wrote:
hey,
I have created this
survey:
OMG! Big +1
to this. I've been trying
to convince people to
start using forks and keep
upstream "celan" for some
time now...
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.
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.
etc.
Thanks!
--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: CodeReady Workspaces
IM: @nickboldt / @nboldt / http://nick.divbyzero.com
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev
--
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev