Gitjk – command to undo what you just did in git(github.com)
github.com
Gitjk – command to undo what you just did in git
https://github.com/mapmeld/gitjk#gitjk
33 comments
Adding it here: http://stackoverflow.com/questions/12589813/whats-a-single-g...
Isn't that what git reflog + reset are for?
Why is sudo hardcoded into so many commands? I'll run your program with privileges if it needs and earned them, thank you very much.
It will print (not run) the command unless you type 'gitjk -f'
When I run 'rm -r' on my machine it warns me about every file in the .git directory.
When I run 'rm -r' on my machine it warns me about every file in the .git directory.
`sudo` is not the best practice with regard to removing that warning, try the `-f` flag instead.
I like how tame and polite your reply is.
Some days are worse than others. Some days I rage out. Other days I realise that some people just don't know something and the best practice is just to educate them rather than raise your blood pressure.
It really depends on how much coffee and sleep I've had. Thanks for the kind words.
It really depends on how much coffee and sleep I've had. Thanks for the kind words.
Thanks! I've amended this in the current version
rm -rf?
[deleted]
sudo hard-coded, and an intolerably stupid name. Next.
Uh... if you want to undo a git add shouldn't you be doing git reset?
somehow when I was testing it, I thought I needed to use rm -r --cached to remove a previously untracked file. It should do git reset in most cases.
Edit: now recommends git reset unless you did "git add ." or something like that.
Edit: now recommends git reset unless you did "git add ." or something like that.
You may have been on your initial commit; in that case, you need to use rm --cached instead of reset to undo a git add.
It does rely on history? Well, it won't work for me then — in my history there's only frequently-used commands.
It's kind of nice that this just gives suggestions by default rather than running potentially breaking commands.
But as someone else here mentioned, you really want to understand the reflog in git. Everyone screws up at some point or another, and it's much easier to work through things when you can rely on the reflog to act as a safety net and an anchor of sanity.
But as someone else here mentioned, you really want to understand the reflog in git. Everyone screws up at some point or another, and it's much easier to work through things when you can rely on the reflog to act as a safety net and an anchor of sanity.
I occasionally wish git had an undo-whatever-I-just-did command, and I've been using it for years.
The git fixup page comes in quite handy. https://sethrobertson.github.io/GitFixUm/fixup.html
The git fixup page comes in quite handy. https://sethrobertson.github.io/GitFixUm/fixup.html
If you name it "git-jk" rather than "gitjk", you can invoke it as
git jkThe gitjk command needs to operate as a shell alias though
[deleted]
Is that specific to git or is it in the shell?
All of the:
git will actually pick up anything in $PATH of the form 'git-<command>' and allow you to run it as 'git <command>'. The downside of this, is that commands of the form:
Edit: Another downside, is that some 'smart' command-line completion settings either have a hard-coded list of 'git <command>' commands, or look for said commands in the value returned by 'git --exec-path'. So you can't tab-complete git-<command> commands that you just drop into $PATH (at least not out of the box).
git <command>
$ git --exec-path
/usr/local/Cellar/git/1.9.0/libexec/git-core
$ ls $(git --exec-path) | head
git
git-add
git-add--interactive
git-am
git-annotate
git-apply
git-archimport
git-archive
git-bisect
git-bisect--helper
git will actually pick up anything in $PATH of the form 'git-<command>' and allow you to run it as 'git <command>'. The downside of this, is that commands of the form:
git <command> --help
man git-<command>
Edit: Another downside, is that some 'smart' command-line completion settings either have a hard-coded list of 'git <command>' commands, or look for said commands in the value returned by 'git --exec-path'. So you can't tab-complete git-<command> commands that you just drop into $PATH (at least not out of the box).
It is specific to git.
Git.
If anyone wants a fish function:
function jk
history | head -n+10 | tail -r | gitjk_cmd
end
The git reflog gets you out of all kinds of messes. https://medium.com/git-tips/a4189dd88c40
rebase isn't very hard to implement; you just have to check the reflog.
Does it work if you call it 2x or more?
I'm pretty sure your fetch logic is not right. First it assumes no arguments are passed. You assume origin/master (which is convention but not guaranteed) and also you assume a refspec isn't passed (in which case you need to rollback FETCH_HEAD).