Re: [che-dev] Eclipse Che: Merged or closed PR

[Oleksandr Garagatyi <ogaragat@xxxxxxxxxx>]

Hi. I want to discuss a topic related to this cleanup. Why not keep branches in dev's own forks? Some Che committers do this and some not. With this approach, we won't need such a cleanup and whole repo would be cleaner. Sure there are cases when multiple ppl work on the same branch but this is a rare case, mostly feature branch is developed by dev and never gets checked out by other community members.

HDYT, should we recommend this approach to committers?

On Wed, Dec 6, 2017 at 9:12 AM, Sergii Kabashniuk <skabashn@xxxxxxxxxx> wrote:

Reminder.

Tomorrow I'll drop branches related to closed or merged PRs.

Next topic.

I want to drop all branches older than 3(discussable value) months. For those

who might interest in that old branches, I may attach bare repository

archive. 

On Tue, Dec 5, 2017 at 1:15 PM, Sergii Kabashniuk <skabashn@xxxxxxxxxx> wrote:

All

Please take a look at your branches

https://github.com/eclipse/che/branches/all

If they are don't needed, or PR is closed or merged, please remove it.

Unless someone notifies me, I'm going to remove  branches

related to closed or merged PRs in a day or two.

Cheers 

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev

--

OLEKSANDR GARAGATYI

SENIOR SOFTWARE ENGINEER

Red Hat