Dealing with pull requests in your local git environment can be done in an easy way, by adding following line to the OFBiz remotes:
fetch = +refs/pull/*/head:refs/remotes/origin/pr/* preferably before the standard fetch line (fetch = +refs/heads/*:refs/remotes/origin/*). This way you can do/have a local checkout for evaluation and testing purposes, before doing an eventual merge into one of the official branches. Best regards, Pierre Smits *Apache Trafodion <https://trafodion.apache.org>, Vice President* *Apache Directory <https://directory.apache.org>, PMC Member* Apache Incubator <https://incubator.apache.org>, committer *Apache OFBiz <https://ofbiz.apache.org>, contributor (without privileges) since 2008* Apache Steve <https://steve.apache.org>, committer On Thu, Jan 30, 2020 at 6:14 PM Mathieu Lirzin <mathieu.lir...@nereide.fr> wrote: > Michael Brohl <michael.br...@ecomify.de> writes: > > > I really don't want to see all kinds of exotic messages coming up in > > our commit history. > > > > If the workflow allows rejecting a pull request because of bad commit > > messages or maybe a hundred commits for a change, I would also be fine > > with it. > > > > My main point is that I'm a bit worried about quality because it is > > much easier to pull in a pull request instead of applying a patch. > > +1 > > I am worried too, Handling pull-requests via Github Web interface makes > really easy to screw the commit history up. > > -- > Mathieu Lirzin > GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37 >
