|Re: [eclipse-pmc] Merge strategy for projects moved to Github|
Ideally we would start to develop a plan / draft document how the new github workflow should look like in general, not only regarding merge policy. Kind regards, Andrey Loskutov Спасение утопающих - дело рук самих утопающих https://www.eclipse.org/user/aloskutov > Gesendet: Mittwoch, 09. Februar 2022 um 16:54 Uhr > Von: "Lars Vogel" <lars.vogel@xxxxxxxxxxx> > An: eclipse-pmc@xxxxxxxxxxx > Betreff: [eclipse-pmc] Merge strategy for projects moved to Github > > Dear PMC members and committers, > > Currently our new Github repo > https://github.com/eclipse-platform/eclipse.platform.releng.aggregator > is set to allow "Allow squash merging" and "Allow rebase merging". > > Allow squash merging: Combine all commits from the head branch into a > single commit in the base branch. > > Allow rebase merging: Add all commits from the head branch onto the > base branch individually. > > Are these the strategies we want to support?
Back to the top