Skip to content

feature request(absorb): automatically restack after absorb #453

Description

@vegerot

IMG_0395

Steps to reproduce:

  • start on a multi-commit stack (6eb in this example)
  • sl prev
  • make some changes and sl absorb
  • notice that the current commit (1b81 in this example) is rewritten but the child (6eb in this example) is not

running sl restack after sl absorb is fine, but I feel like absorb should just do it.

Can anyone think of a downside to restacking after an absorb?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions