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:
This feels good. Need to make this a lib or something.
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. #UFC321 42.6K posts
- 2. Arbuckle 1,157 posts
- 3. UCLA 6,236 posts
- 4. Sunderland 106K posts
- 5. Lane Kiffin 4,311 posts
- 6. Cam Coleman 1,051 posts
- 7. Jackson Arnold N/A
- 8. Cunha 50.5K posts
- 9. Anthony Taylor 8,462 posts
- 10. Oklahoma 13.2K posts
- 11. Lamar 16.7K posts
- 12. Sark 2,799 posts
- 13. Delgado 13.7K posts
- 14. Welbeck 6,867 posts
- 15. #iufb 1,650 posts
- 16. Tosin 27.1K posts
- 17. Chambliss N/A
- 18. Valter Walker 5,091 posts
- 19. Chelsea 204K posts
- 20. #Huskers N/A
Something went wrong.
Something went wrong.