4 ms·
If you're stashing your changes, that means they're just in the working copy and haven't been committed to the incorrect branch. In this case, simply create th
by spinningarrow 10y ago
If you're stashing your changes, that means they're just in the working copy and haven't been committed to the incorrect branch.
In this case, simply create the branch and switch to it (git checkout -b branchname) and you're good. It's like it never happened ;) (remember that branches are just labels - until you commit it doesn't really matter).
- ryanSrich 10y agoTypically once I've noticed I haven't branched is after I've already added and committed.
- sammoth 10y agoThen just create the branch where you are, and afterwards go back and reset the original branch
- convolvatron 10y agoand make sure to patch up the upstream reference