Skip to content

Interactive rebase order is backwards #1190

@mbarak

Description

@mbarak

Issue Type: Bug

in the terminal:

export EDITOR="code -w"
git rebase -i master

Extension version: 11.0.1
VS Code version: Code 1.51.1 (e5a624b788d92b8d34d1392e4c4d9789406efe8f, 2020-11-11T01:11:34.018Z)
OS version: Darwin x64 19.6.0

System Info
Item Value
CPUs Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
webgl: enabled
webgl2: enabled
Load (avg) 3, 3, 2
Memory (System) 32.00GB (3.85GB free)
Process Argv --crash-reporter-id 4691b649-08b6-4699-93cc-24b45479e024
Screen Reader no
VM 0%

The order of commits in the gitlens interactive rebase editor is backwards.

In regular git on the terminal, the commits are ordered in the order they will be applied.
Top commit will be applied first, then the next, etc.

In gitlens this is backwards.

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions