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 Trends
- 1. Brian Kelly 8,469 posts
- 2. #VERZUZ 45.6K posts
- 3. Yamamoto 38.2K posts
- 4. Birdman 11.8K posts
- 5. No Limit 30.7K posts
- 6. Mia X 575K posts
- 7. Cash Money 26.8K posts
- 8. Wayne 36.4K posts
- 9. #HalloweenHavoc 46.1K posts
- 10. Turk 572K posts
- 11. Jonas Brothers 5,807 posts
- 12. Tamar 7,844 posts
- 13. Michigan 35.1K posts
- 14. Texas A&M 8,469 posts
- 15. Master P 6,684 posts
- 16. Snoop 10.1K posts
- 17. Death Valley 2,705 posts
- 18. #Dodgers 16.6K posts
- 19. Nuss 3,207 posts
- 20. Sixers 7,805 posts
Something went wrong.
Something went wrong.