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. #SmackDown 13.2K posts
- 2. #WorldSeries 65.6K posts
- 3. Snell 6,247 posts
- 4. Halo 133K posts
- 5. Darryn Peterson 1,352 posts
- 6. PlayStation 63K posts
- 7. Purdue 5,998 posts
- 8. Celtics 16.9K posts
- 9. $BIEBER N/A
- 10. Knicks 20.4K posts
- 11. Jade Cargill N/A
- 12. #LetsGoDodgers 5,638 posts
- 13. Xbox 76.2K posts
- 14. Cole Anthony N/A
- 15. Zion 13.8K posts
- 16. End of 1 13.9K posts
- 17. Tyler Kolek 1,312 posts
- 18. Yesavage 6,416 posts
- 19. Andy Pages N/A
- 20. End 1Q N/A
Something went wrong.
Something went wrong.