Okay, one more... Ever commit something only to immediately realize that you're on the wrong branch? Use "git move <branch>".
Interesting… I typically commit, cut a branch, reset current. Find it doesn't disrupt my workflow and avoids complex commands like stash.
That approach requires three checkouts if you want to end up on new branch, hence the stashing.
You need to collect these in a blog post or something, so they don't get lost in the depths of Twitter.
Agreed. They're in my .gitconfig so they're there whenever I get around to blogging again... I've got quite a backlog.
I would have thought cherry-pick then reset head would be a *lot* cleaner....
It's pick your poison, really. Here's the same end result using cherry-pick:
I personally just "git checkout -b NEWBRANCH" then go back to the previous branch and reset to the last good commit
So... three checkouts by the time you get back to the new branch to continue working?
Later in the thread we evolved it to a branch, rebase onto, checkout three step, though works only for existing branches.
Not so much. Here's the same end result using cherry-pick:
It could use a graceful failure when omitting the new branch name, also should confirm branch creation if it doesn't exist. But, yeah. :)
If junio can trust it, why not try to push it to the project instead? If junio can trust it.
United States トレンド
- 1. Jets 118K posts
- 2. Sauce 83K posts
- 3. Courtois 43.6K posts
- 4. Colts 56.7K posts
- 5. Breece Hall 11K posts
- 6. $JFB N/A
- 7. Liverpool 225K posts
- 8. Garrett Wilson 5,250 posts
- 9. Cheney 240K posts
- 10. Beane 5,412 posts
- 11. Luis Diaz 33.1K posts
- 12. Veach 5,862 posts
- 13. Penning 3,132 posts
- 14. Shaheed 17.5K posts
- 15. Brad Holmes 1,242 posts
- 16. Hakimi 32.3K posts
- 17. Real Madrid 183K posts
- 18. Bayern 116K posts
- 19. AD Mitchell 6,735 posts
- 20. Mazi Smith 6,167 posts
Something went wrong.
Something went wrong.