Jonah,
+1 for fast-forward-only
In principle that could force one to rebase and then kick off another CI
Bot verification job, but that's not so likely to occur much in practice.
Cheers,
Ed
On 13.11.2018 09:55, Jonah Graham wrote:
Hi Ed,
If you want you can do a "Rebase" in the Gerrit UI
Hi
Ah! It never occurred to me that "Reply" meant "Commit" / "Push" /
"Merge" or even "Review". I saw only "Cherry Pick" / " Cancel" which did
not match my requirements. What a truly awful UI.
What if I don't want to "Merge" since it leads to double history entries
that on normal projects
Hi Ed,
If you want you can do a "Rebase" in the Gerrit UI before doing the Submit.
Alternatively, and what I personally prefer is to set gerrit's merge
strategy to either Fast forward only, or rebase. The Eclipse platform uses
fast forward only. This prevents any merge commits and ensures that
Hi,
I have changed the submit type to "fast-forward only" for the
simrel/org.eclipse.simrel.build repo.
Regards,
Fred
On 13.11.18 10:10, Ed Merks wrote:
> Jonah,
>
> +1 for fast-forward-only
>
> In principle that could force one to rebase and then kick off another CI
> Bot verification job,
Compiled 2018-11-13-13:30:01
Projects exceeding 80G of disk space on HIPP/JIPPs:
===
1.1T /jobs/genie.packaging
187G /jobs/genie.openj9
116G /jobs/genie.xtext
101G /jobs/genie.platform
92G /jobs/genie.capella
89G /jobs/genie.osee
82G /jobs/genie.ice
