Page MenuHomePhabricator

Add a check for ambiguous merge strategies after the "history.immutable" behavioral change
ClosedPublic

Authored by epriestley on Jun 8 2020, 1:40 PM.
Tags
None
Referenced Files
F18978803: D21332.id.diff
Sun, Nov 16, 8:49 PM
F18978218: D21332.diff
Sun, Nov 16, 7:30 PM
F18922329: D21332.id.diff
Sun, Nov 9, 3:21 PM
F18905588: D21332.diff
Sat, Nov 8, 2:41 PM
F18857864: D21332.id50762.diff
Nov 1 2025, 6:36 PM
F18802861: D21332.id50762.diff
Oct 17 2025, 8:42 PM
F18802859: D21332.id50795.diff
Oct 17 2025, 8:42 PM
F18797126: D21332.diff
Oct 17 2025, 4:40 AM
Subscribers
None

Details

Summary

Ref T13546. When users hit a situation where we would select "squash" but would previously select "merge", prevent them from continuing under ambiguous conditions.

Test Plan

Ran "arc land" in Git with "history.immutable" true, false, and not configured.

Diff Detail

Repository
rARC Arcanist
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was not accepted when it landed; it landed in state Needs Review.Jun 8 2020, 11:26 PM
This revision was automatically updated to reflect the committed changes.