Closed Bug 1105394 Opened 10 years ago Closed 6 years ago

Preemptive merge notification when pushing against an old head

Categories

(MozReview Graveyard :: General, defect, P4)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: gps, Unassigned)

Details

This applies to both Try and MozReview, but I'm filing against MozReview for right now. General problem: Someone starts developing a patch against changeset N. By the time they push the patch to Try or MozReview, the repo is already at changeset N + M and there is bit rot. I think it would be rad if at push time the server automatically detected the scenario where pushed changes are touching files that have been changed in the current repo head and it proactively notifies the user, encouraging them to do a pull + rebase to ensure their push is up to date. Going one step further, we can have the server automatically rebase pushes on top of the latest head. Facebook is developing an extension to do this. I expect them to make it open source when it is ready.
Priority: -- → P3
We have too many P1s, so I'm spreading out the priorities. P3 -> P4, P2 -> P3, and some portion of P1s will become P2.
Priority: P3 → P4
Product: Developer Services → MozReview
MozReview is now obsolete. Please use Phabricator instead. Closing this bug.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.