Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relocate branches #1615

Open
CLOVIS-AI opened this issue Mar 13, 2023 · 2 comments
Open

Relocate branches #1615

CLOVIS-AI opened this issue Mar 13, 2023 · 2 comments
Labels
externally requested feature New feature or request

Comments

@CLOVIS-AI
Copy link

Feature description

Git Machete shines with the "rebase to edit the current branch" workflow, but I think it could be better with the "rebase to change the base of a branch" workflow.

Examples:

  • Move up the hierarchy (becomes its parent's sibling): rebase from the base of the parent branch, drop all commits which are in the parent but not the child
  • Move down the hierarchy (becomes its sibling's child): rebase from the base of the branch onto the new child

Both of these are easily doable today for users who understand Git well (edit the .machete file manually then use Machete to rebase and drop what shouldn't be there), but I think they could be made easier to use? Maybe by drag-and-drop'ing in the tool window?

@CLOVIS-AI CLOVIS-AI added externally requested feature New feature or request labels Mar 13, 2023
@mkondratek
Copy link
Collaborator

This idea has almost 3 years already (#231) 😅

I agree that it would be very handy to be able to drag & drop the branches and more convenient than the machete file edition. 👍

As you can see in the original issue we had decided to drop this idea as

  • there is the mentioned workaround with editing the machete file 🔧
  • it seems to be complicated - drag&drop handling indentions, multiple separate root branches, looking and working nice, developed by programmers by engineers with backend experience only 😅

However, as this time the issue has been brought up from outside (by you!) we surely reconsider it 🙂

@CLOVIS-AI
Copy link
Author

Ahah, I understand your points. You're right, the workaround is easy (at least for developers who understand Git well). Feel free to close this as duplicate if you want to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
externally requested feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants