if I'm in a branch: fix-1, then git stash, then git checkout fix-2, then git stash pop, I now have the working copy changes from fix-1 on my working copy of fix-2. Will the UI support applying a stash from one branch to another branch? e.g. In one of my workflows I'm often using the stash to persist working copy changes that I can't commit but are required to get my local copy working (don't ask why.legacy code.). It would be awesome to have this same level of control in the GUI. Why not give users the ability to control the full stash instead of limiting to a single entry per branch? It's a stack, so there's nothing in git itself preventing users from having multiple stashes if they use the CLI. Up late trying to fix it, any help would be. I tried git fsck -unreachable, but there is a lot to sort through and I didnt see it anywhere. if you already have a stash, we'll need to also warn that stashing again will overwrite the existing stash, just like we do in the switching branches stashing flow. I meant to stash my changes so I could see what my project was like before my changes, but when I went to bring it back I had accidentally overridden my stash. It'll continue to use the same paradigm that exists today, where you can't have multiple stashes per branch. Select one or more files in the changes tab > right click > new option for "Stash selected files".New Stashes tab (next to Changes/History): Similar to the History tab, displays a list of all stashes in the stack with context menu options for each to apply a specific stash to the working copy.New Branch menu option: "Apply last stash to working copy" (equivalent to git stash pop). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |