New issue
Advanced search Search tips

Issue 693351 link

Starred by 1 user
Status: Duplicate
Merged: issue 682883
Owner: ----
Closed: Feb 2017
Cc:
qyears...@chromium.org
jeffcarp@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 657117



Sign in to add a comment

[WPT Export] Use "Rebase and merge" strategy instead of creating merge commits

Project Member Reported by foolip@chromium.org, Feb 17 2017 
In  issue 693350  the exporter has exported the same thing over and over.

One mitigation for this kind of problem might be to use the "Rebase and merge" when merging PRs. Even if the PR branch is based on something slightly out of date, trying to rebase should then result in no changes and fail.

Maybe? Not sure :)

Comment 1 by qyears...@chromium.org, Feb 17 2017 

Related:  bug 682883 . (Not sure if this bug should be duped into that one.) I'm not sure I understand, but I think we wanted to change to rebase before merging PRs, but it's behaving like we expected it to?

Comment 2 by jeffcarp@chromium.org, Feb 18 2017 

I think this should be duped into  bug 682883 . The CL I made for that bug - https://crrev.com/2658713002 - doesn't seem to have had the desired effect. I'll debug.

Comment 3 by qyears...@chromium.org, Feb 19 2017

Mergedinto: 682883
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment