Some of these changes may also be staged in the index. How git stash encodes your worktree and index as commits:īefore stashing, your worktree may contain changes to tracked files, untracked files, and ignored files. you specified the -include-untracked or -all option when invoked git stash. h Go to file Go to fileT Go to lineL Copy path Copy This commit does not belong to any branch on this repository.your working copy actually contained untracked files and.third parent, a new commit representing untracked files that were in your working copy when you ran git stash. second parent, a new commit representing the index when you ran git stash.first parent, the pre-existing commit that was at HEAD when you ran git stash.a new commit to store the tracked files that were in your working copy when you ran git stash.953ddde WIP on main: 5002d47 our new homepage |\ \ | | * 24b35a1 untracked files on main: 5002d47 our new homepage | * 7023dd4 index on main: 5002d47 our new homepage |/ * 5002d47 our new homepageĭepending on what you stashed, a single git stash operation creates either two or three new commits. Instead, you can use git stash branch to create a new branch to apply your stashed changes *. If the changes on your branch diverge from the changes in your stash, you may run into conflicts when popping or applying your stash. There is no explicit "abort" command, but hitting CTRL-C(SIGINT) will abort the stash process. Quit (any hunks that have already been selected will be stashed) You can hit ? for a full list of hunk commands.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |