Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Possible new commands #3

Closed
1 of 10 tasks
arxanas opened this issue Jan 12, 2021 · 1 comment
Closed
1 of 10 tasks

Possible new commands #3

arxanas opened this issue Jan 12, 2021 · 1 comment

Comments

@arxanas
Copy link
Owner

arxanas commented Jan 12, 2021

  • git top/git bottom to traverse an entire series of commits. (Names need to be revised, since the ordering may be reverse of what's expected.)
  • Interactive git checkout, operating on nodes on the smartlog graph. Could include fuzzy-filtering or EasyMotion-style commit selection.
  • git move as a replacement for git rebase, to move entire subtrees. Proposal: --dest, --base, --restack, and --main flags.
  • git sync XXX to rebase in-progress work onto main branch (or git sync --all, or git sync --onto).
  • git stage to interactively stage a commit. Should see what tig does for this.
  • git split to split the current commit (or a provided commit) using repeated git stages. Splitting should not check out to a different commit, since it shouldn't affect the working copy.
  • git absorb (there's already an implementation of git absorb out there, but it doesn't work unless you have a branch checked out). Absorbing should not check out to a different commit, since it shouldn't affect the working copy.
  • git amend to amend the current commit contents, but not its message. May automatically restack, or have an option to automatically restack?
  • git reword to amend the current commit message, but not its contents. Should be able to safely automatically restack, since it doesn't touch the working copy.
  • git uncommit as a replacement for git reset --soft HEAD^, since the latter is unergonomic, and it doesn't hide the given commit from the smartlog. It may be desirable to unstage the previously-committed changes as well; I've never personally wanted to keep them staged after a git reset --soft HEAD^.
@krobelus
Copy link

krobelus commented May 2, 2021

git absorb (there's already an implementation of git absorb out there, but it doesn't work unless you have a branch checked out).

https://github.com/torbiak/git-autofixup/ should do the job

@arxanas arxanas closed this as completed Jun 28, 2021
Repository owner locked and limited conversation to collaborators Jun 28, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants