Closed Bug 1175214 Opened 9 years ago Closed 7 years ago

Automatically enable pushrebase when pushing to Firefox repos

Categories

(Developer Services :: Mercurial: firefoxtree, defect)

Product:
Developer Services
Component:
Mercurial: firefoxtree
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: gps, Assigned: gps)

References

Details

We enabled the pushrebase extension on hg.mozilla.org in bug 1117857. We should have firefoxtree use server-side rebasing automatically.
As part of working on this, I discovered the following limitations:

* Changeset count when pushrebase is used is incorrect (possible core Mercurial bug, possible pushrebase bug)
* Server side output is dropped when pushing with pushrebase unless a rebase has been performed (almost certainly a bug with pushrebase)
* Client w/o evolve enabled will have 2 copies of commit in the local repository: the local, unrebased version and the remote, rebased version
* The "afterloaded" extension dependency functionality I added to Mercurial is buggy. This means auto-adding --onto during push operations may not always work.

I'd like to get a few of these fixed before I recommend using pushrebase.
Apparently Facebook made a number of updates to pushrebase recently. Someone should reevaluate to see if the issues in comment #1 are still relevant.
We removed the copy of the pushrebase extension from version-control-tools in 15bfb39d33eb. We have no plans to roll it out to hg.mozilla.org at this time. Autoland is the future.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.