{"id":30817,"date":"2022-07-24T14:17:08","date_gmt":"2022-07-24T14:17:08","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=30817"},"modified":"2022-12-23T05:48:04","modified_gmt":"2022-12-23T05:48:04","slug":"git-lab-exercise-assignment-git-stash-part-11","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/git-lab-exercise-assignment-git-stash-part-11\/","title":{"rendered":"Git Lab Exercise & Assignment: Git Stash: Part – 11"},"content":{"rendered":"\n

Often, when you\u2019ve been working on part of your project, things are in a messy state and you want to switch branches for a bit to work on something else. The problem is, you don\u2019t want to do a commit of half-done work just so you can get back to this point later. The answer to this issue is the git stash command.

You can also put it somthing like this, Your code is in progress and suddenly a customer escalation comes. Because of this, you have to keep aside your new feature work for a few hours. You cannot commit your partial code and also cannot throw away your changes. So you need some temporary space, where you can store your partial changes and later on commit it.

Stashing takes the dirty state of your working directory \u2013 that is, your modified tracked files and staged changes \u2013 and saves it on a stack of unfinished changes that you can reapply at any time.<\/strong><\/p>\n\n\n\n

\n\n\n
\r\n# Modify | Add  Some files in Git working directory<\/span>\r\n$ git status\r\nNow you want to switch<\/span> branches, but you don\u2019t want to commit what you\u2019ve been working on yet; so you\u2019ll stash the changes. To push a new<\/span> stash onto your stack, run git stash or<\/span> git stash save:\r\n\r\n\r\n$ git stash\r\nYour working directory is clean:\r\n\r\n\r\n$ git status\r\nAt this point, you can easily switch<\/span> branches and<\/span> do<\/span> work elsewhere; your changes are stored on your stack. To see which stashes you\u2019ve stored, you can use<\/span> git<\/span> stash<\/span> list<\/span>:\r\n\r\n\r\n$ git<\/span> stash<\/span> list<\/span>\r\nstash<\/span>@{0}: WIP<\/span> on<\/span> master<\/span>: 049d078<\/span> added<\/span> the<\/span> index<\/span> file<\/span>\r\nstash<\/span>@{1}: WIP<\/span> on<\/span> master<\/span>: c264051<\/span> Revert<\/span> \"added<\/span> file_size<\/span>\"\r\nstash<\/span>@{2}: WIP<\/span> on<\/span> master<\/span>: 21d80a5<\/span> added<\/span> number<\/span> to<\/span> log<\/span>\r\nIf<\/span> you<\/span> want<\/span> to<\/span> apply<\/span> one<\/span> of<\/span> the<\/span> older<\/span> stashes<\/span>, you<\/span> can<\/span> specify<\/span> it<\/span> by<\/span> naming<\/span> it<\/span>, like<\/span> this<\/span>: git<\/span> stash<\/span> apply<\/span> stash<\/span>@{2}.\r\n\r\n\r\n$git<\/span> stash<\/span> apply<\/span> stash<\/span>@{2}\r\nIf<\/span> you<\/span> don<\/span>\u2019t<\/span> specify<\/span> a<\/span> stash<\/span>, Git<\/span> assumes<\/span> the<\/span> most<\/span> recent<\/span> stash<\/span> and<\/span> tries<\/span> to<\/span> apply<\/span> it<\/span>:\r\n\r\n\r\n$ git<\/span> stash<\/span> apply<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>","protected":false},"excerpt":{"rendered":"
Often, when you\u2019ve been working on part of your project, things are in a messy state and you want to switch branches for a bit to work on something else. The problem is, you don\u2019t want to do a commit of half-done work just so you can get back to this point later. The answer…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","_joinchat":[],"footnotes":""},"categories":[2],"tags":[],"class_list":["post-30817","post","type-post","status-publish","format-standard","hentry","category-uncategorised"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/30817","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=30817"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/30817\/revisions"}],"predecessor-version":[{"id":30818,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/30817\/revisions\/30818"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=30817"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=30817"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=30817"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}