Skip to content

git move cannot move remote commit as expected #1452

Closed

Description

@HAOCHENYE

Description of the bug

Current Situation

I have two branches:

  • Branch A (remote: origin/A): Commit history a <- b <- c
  • Branch B: Commit history a <- d <- e

Expected Behavior

When using git move -s <b commit> -d <e>, I expected all descendants of the moved commit to be included.

Actual Behavior

The result is a <- d <- e <- b, with b's child commit c not being moved.

Question

Is this the intended behavior of the git move command? If not, could this be considered a bug?

Additional Context

  • Parent commit: a
  • Moved commits: b
  • Destination: Commit e

Expected behavior

No response

Actual behavior

No response

Version of rustc

No response

Automated bug report

No response

Version of git-branchless

git-branchless-opts 0.10.0

Version of git

git version 2.34.1

Activity

  1. Repository owner locked and limited conversation to collaborators on Nov 25, 2024
  2. converted this issue into a discussion #1454 on Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions