{"id":17352,"date":"2026-01-21T16:21:41","date_gmt":"2026-01-21T10:51:41","guid":{"rendered":"https:\/\/www.youstable.com\/blog\/?p=17352"},"modified":"2026-01-21T16:21:43","modified_gmt":"2026-01-21T10:51:43","slug":"git-stash-command","status":"publish","type":"post","link":"https:\/\/www.youstable.com\/blog\/git-stash-command","title":{"rendered":"Git Stash Command Explained With Simple Examples in 2026"},"content":{"rendered":"\n<p><strong>Git stash temporarily shelves your uncommitted changes<\/strong> so you can switch branches, pull updates, or run tests on a clean working tree without losing work.<\/p>\n\n\n\n<p>It saves modified files (and optionally untracked\/ignored files) into a stack like storage, letting you reapply them later via <code>git stash apply<\/code> or remove and apply in one step with <code>git stash pop<\/code>. <\/p>\n\n\n\n<p>If you\u2019ve ever needed to pause what you\u2019re doing, switch tasks, and return without losing progress, the <strong>git stash<\/strong> command is your best friend. <\/p>\n\n\n\n<p>In this guide, I\u2019ll explain the Git stash command with simple examples, pro tips, and common pitfalls based on real workflows used in hosting, CI\/CD, and collaborative teams.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"what-is-git-stash-and-how-does-it-work\">What is Git Stash and How Does it Work?<\/h2>\n\n\n\n<p><strong>Git stash<\/strong> takes your dirty working directory (changes not yet committed) and stores those changes in a special stack referenced by <code>refs\/stash<\/code>. Your working directory is then cleaned to match HEAD, letting you switch branches or pull without conflicts. Later, you can reapply the stashed changes to any branch.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"what-gets-stashed\">What Gets Stashed?<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Tracked changes:<\/strong> Modified files that Git already tracks.<\/li>\n\n\n\n<li><strong>Untracked files: <\/strong>Only if you use <code>--include-untracked<\/code> or <code>-u<\/code>\/<code>-a<\/code>.<\/li>\n\n\n\n<li><strong>Ignored files:<\/strong> Only if you use <code>--all<\/code>.<\/li>\n\n\n\n<li><strong>Index vs working tree<\/strong>: You can control whether staged changes are kept staged using <code>--keep index<\/code>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"when-to-use-git-stash\">When to Use Git Stash<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You need to <strong>switch branches<\/strong> but have local edits you\u2019re not ready to commit.<\/li>\n\n\n\n<li>You want to <strong>pull\/rebase<\/strong> cleanly without committing partial work.<\/li>\n\n\n\n<li>You\u2019re <strong>experimenting<\/strong> and want a safe temporary snapshot.<\/li>\n\n\n\n<li>Your <strong>CI\/CD<\/strong> or staging workflow requires a clean working tree to test a build.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"quick-start-the-most-useful-git-stash-commands\">Quick Start: The Most Useful Git Stash Commands<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"create-a-stash-save-push\">Create a Stash (save\/push)<\/h3>\n\n\n\n<p>Modern Git uses <code>git stash push<\/code> (equivalent to <code>git stash<\/code> in many cases). Add a message so you recognize it later.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Stash tracked changes with a message\ngit stash push -m \"WIP: homepage layout tweak\"\n\n# Include untracked files (e.g., new files)\ngit stash push -u -m \"WIP: add ContactForm component\"\n\n# Include ignored files too (rare)\ngit stash push -a -m \"Temp build outputs stashed\"<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"see-your-stashes\">See Your Stashes<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>git stash list\ngit stash show -p stash@{0}   # show patch of a specific stash<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"reapply-vs-reapply-and-remove\">Reapply vs Reapply and Remove<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Apply<\/strong> replays changes but <em>keeps<\/em> the stash: <code>git stash apply<\/code><\/li>\n\n\n\n<li><strong>Pop<\/strong> replays changes and <em>removes<\/em> the stash: <code>git stash pop<\/code><\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code># Apply the most recent stash\ngit stash apply\n\n# Apply a specific stash\ngit stash apply stash@{2}\n\n# Pop (apply and remove)\ngit stash pop\ngit stash pop stash@{1}<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"clean-up-stashes\">Clean Up Stashes<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Remove one stash\ngit stash drop stash@{0}\n\n# Remove all stashes\ngit stash clear<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"create-a-branch-from-a-stash\">Create a Branch From a Stash<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Great for turning WIP into a feature branch\ngit stash branch feature\/new-ui stash@{0}<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"practical-git-stash-examples-step-by-step\">Practical Git Stash Examples (Step-by-Step)<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"1-stash-local-edits-to-pull-the-latest-code\">1) Stash Local Edits to Pull the Latest Code<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># You have uncommitted changes on main\ngit stash push -m \"WIP: optimize hero image\"\n\n# Get the latest changes safely\ngit pull --rebase\n\n# Reapply your work\ngit stash pop<\/code><\/pre>\n\n\n\n<p>Keeps your history clean and reduces merge conflicts by rebasing onto fresh upstream commits.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"2-stash-only-certain-files\">2) Stash Only Certain Files<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Only stash changes in src\/components\ngit stash push -m \"WIP: components only\" -- src\/components\n\n# Only stash a single file\ngit stash push -m \"WIP: header styles\" -- src\/styles\/header.css<\/code><\/pre>\n\n\n\n<p>Pathspecs let you limit the scope of your stash, perfect for large repos where unrelated changes shouldn\u2019t be touched.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"3-stash-untracked-or-ignored-files\">3) Stash Untracked or Ignored Files<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Include untracked files\ngit stash push -u -m \"WIP: new config files\"\n\n# Include everything (tracked, untracked, ignored)\ngit stash push -a -m \"WIP: stash node_modules &amp; build\"<\/code><\/pre>\n\n\n\n<p>Use <code>-a<\/code> cautiously. Stashing large ignored folders (like <code>node_modules\/<\/code>) can be slow and is rarely necessary.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"4-resolve-conflicts-after-applying-a-stash\">4) Resolve Conflicts After Applying a Stash<\/h3>\n\n\n\n<p>If <code>apply<\/code> or <code>pop<\/code> results in conflicts, Git marks files just like a merge conflict. Fix them, then mark as resolved.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># After conflicts occur\ngit status\n# Edit files and resolve conflict markers\ngit add &lt;resolved-files&gt;\n# If you used pop and conflicts happened, the stash may still exist until resolution completes<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"5-convert-a-stash-into-a-feature-branch\">5) Convert a Stash Into a Feature Branch<\/h3>\n\n\n\n<p>Turn work in progress into its own branch without affecting your current one.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>git stash branch feature\/login-ui stash@{0}\n# Now commit changes on the new branch<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"advanced-git-stash-techniques\">Advanced Git Stash Techniques<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"add-a-descriptive-message\">Add a Descriptive Message<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Always describe your stash for future you (or teammates)\ngit stash push -m \"WIP: refactor API client for retries\"<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"keep-staged-changes-staged\">Keep Staged Changes Staged<\/h3>\n\n\n\n<p>Use <code>--keep-index<\/code> to stash only unstaged changes. Perfect when your commit is half ready but you need to pause.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Keeps staged changes intact; stashes only unstaged edits\ngit stash push --keep-index -m \"Pause: tests failing, keep staged fix\"<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"stash-interactively-patch-mode\">Stash Interactively (Patch Mode)<\/h3>\n\n\n\n<p>Choose specific hunks to stash, useful when a file contains both ready to commit and still experimental parts.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>git stash push -p -m \"WIP: stash only parts of file\"<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"compare-apply-vs-pop-vs-branch\">Compare Apply vs Pop vs Branch<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>apply:<\/strong> Safest when you\u2019re not sure it\u2019ll cleanly reapply (the stash remains if conflicts occur).<\/li>\n\n\n\n<li><strong>pop:<\/strong> Faster when confident, applies and removes the stash in one step.<\/li>\n\n\n\n<li><strong>branch:<\/strong> Best for isolating WIP into its own branch for code review or CI.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"common-mistakes-and-how-to-avoid-them\">Common Mistakes and How to Avoid Them<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Forgetting what\u2019s in a stash:<\/strong> Always use <code>-m<\/code> messages and <code>git stash show -p<\/code> before applying.<\/li>\n\n\n\n<li><strong>Using pop when conflicts are likely:<\/strong> Prefer <code>apply<\/code>, verify the result, then manually <code>drop<\/code>.<\/li>\n\n\n\n<li><strong>Stashing massive ignored folders:<\/strong> Avoid <code>-a<\/code> unless essential. It slows down operations and can bloat your repo metadata.<\/li>\n\n\n\n<li><strong>Relying on stash as a long term storage:<\/strong> Stash is for short term task switching. Convert to a branch when work extends beyond a day.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"real-world-workflow-teams-ci-cd-and-hosting\">Real World Workflow: Teams, CI\/CD, and Hosting<\/h2>\n\n\n\n<p><strong>In fast moving teams<\/strong>, you\u2019ll often stash to run quick hotfixes or pull updates before a release. Combined with code review and CI, stash keeps your working copy clean without polluting history with \u201cWIP\u201d commits.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Before rebasing:<\/strong> <code>git stash push<\/code>, <code>git pull --rebase<\/code>, then <code>git stash pop<\/code>.<\/li>\n\n\n\n<li><strong>Before urgent hotfix:<\/strong> Stash your current work, checkout hotfix branch, patch, deploy, then return and pop.<\/li>\n\n\n\n<li><strong>For staging\/testing:<\/strong> Keep WIP out of the staging branch; convert critical stashes into a feature branch (<code>git stash branch ...<\/code>) for CI tests.<\/li>\n<\/ul>\n\n\n\n<p><strong>If you use managed hosting with Git workflows<\/strong>, look for staging environments that support branch based deployments. At <strong><a href=\"https:\/\/www.youstable.com\/\">YouStable<\/a><\/strong>, our developer friendly hosting makes it easy to spin up staging sites per branch, so you can turn a <code>git stash<\/code> into a proper feature branch and test changes safely, without risking production.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"troubleshooting-git-stash\">Troubleshooting Git Stash<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"where-did-my-stash-go\">\u201cWhere Did My Stash Go?\u201d<\/h3>\n\n\n\n<p>Run <code>git stash list<\/code>. If you accidentally dropped a stash, check the reflog. Stash entries are commits; sometimes you can recover them.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Show stash stack\ngit stash list\n\n# Inspect HEAD and stash movements\ngit reflog\n\n# If you spot the lost commit hash, create a branch to recover\ngit branch rescue &lt;commit-hash&gt;<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"applied-the-wrong-stash\">Applied the Wrong Stash<\/h3>\n\n\n\n<p>Use <code>git reset --hard<\/code> to revert your working tree to a known commit (careful: discards uncommitted changes). Or commit the unintended state and revert via a new commit, safer on shared branches.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"stash-conflicts-on-apply-pop\">Stash Conflicts on Apply\/Pop<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Inspect conflicts:<\/strong> <code>git status<\/code><\/li>\n\n\n\n<li><strong>Resolve markers in files:<\/strong> <code>&lt;&lt;&lt;&lt;&lt;&lt;&lt;<\/code>, <code>=======<\/code>, <code>&gt;&gt;&gt;&gt;&gt;&gt;&gt;<\/code><\/li>\n\n\n\n<li><strong>Mark resolved: <\/strong><code>git add<\/code><\/li>\n\n\n\n<li><strong>Complete the apply:<\/strong> if using <code>pop<\/code>, ensure it finished; otherwise re-apply carefully<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"best-practices-for-using-git-stash\">Best Practices for Using Git Stash<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Prefer small, frequent commits<\/strong> for shareable work; use stash for short, private context switches.<\/li>\n\n\n\n<li><strong>Name your stashes<\/strong> with <code>-m<\/code> for clarity during busy sprints.<\/li>\n\n\n\n<li><strong>Use apply before pop<\/strong> when you anticipate conflicts or are reapplying across branches.<\/li>\n\n\n\n<li><strong>Convert long lived stashes<\/strong> into feature branches: <code>git stash branch<\/code>.<\/li>\n\n\n\n<li><strong>Keep the stack tidy<\/strong>: drop or clear stashes you no longer need.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"git-stash-command-reference-cheat-sheet\">Git Stash Command Reference (Cheat Sheet)<\/h2>\n\n\n\n<pre class=\"wp-block-code\"><code># Save changes\ngit stash push -m \"message\"\ngit stash push -u -m \"include untracked\"\ngit stash push -a -m \"include ignored\"\n\n# Inspect\ngit stash list\ngit stash show -p stash@{n}\n\n# Reapply\ngit stash apply &#91;stash@{n}]\ngit stash pop &#91;stash@{n}]\n\n# Remove\ngit stash drop &#91;stash@{n}]\ngit stash clear\n\n# Branch from stash\ngit stash branch &lt;branch-name&gt; &#91;stash@{n}]\n\n# Partial\/interactive\ngit stash push -p -m \"partial stash\"\n\n# Keep staged changes\ngit stash push --keep-index -m \"keep index\"<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"faqs\">FAQ&#8217;s<\/h2>\n\n\n<div id=\"rank-math-faq\" class=\"rank-math-block\">\n<div class=\"rank-math-list \">\n<div id=\"faq-question-1768631557672\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"1-what-does-git-stash-actually-store-and-where\">1. What does git stash actually store and where?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Each stash is a set of commits stored under <code>refs\/stash<\/code>. It typically includes a commit for the index (staged changes) and working tree (unstaged changes). You can view them with <code>git stash list<\/code> and inspect contents via <code>git stash show -p<\/code>.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1768631565306\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"2-whats-the-difference-between-git-stash-apply-and-pop\">2. What\u2019s the difference between git stash apply and pop?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p><code>apply<\/code> reapplies changes but keeps the stash so you can try again or use it elsewhere. <code>pop<\/code> reapplies changes and removes the stash entry. If conflicts are likely, use <code>apply<\/code> first, then <code>drop<\/code> after success.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1768631573770\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"3-how-do-i-stash-untracked-files-or-ignored-files\">3. How do I stash untracked files or ignored files?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Use <code>-u<\/code>\/<code>--include-untracked<\/code> to stash untracked files, and <code>-a<\/code>\/<code>--all<\/code> to include ignored files too. Example: <code>git stash push -u -m \"stash new files\"<\/code> or <code>git stash push -a -m \"stash everything\"<\/code>.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1768631580350\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"4-can-i-stash-only-specific-files-or-parts-of-a-file\">4. Can I stash only specific files or parts of a file?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Yes. Limit by path: <code>git stash push -- path\/to\/file<\/code>. For partial changes, use interactive mode: <code>git stash push -p<\/code> to select hunks line by line.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1768631587148\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"5-is-git-stash-safe-for-long-term-storage\">5. Is git stash safe for long-term storage?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Stash is designed for short-term task switching. For longer work, convert a stash into a branch using <code>git stash branch &lt;name&gt;<\/code>. That way, CI, code review, and collaboration workflows can proceed normally.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"conclusion\">Conclusion<\/h2>\n\n\n\n<p><strong>Git stash<\/strong> is a powerful safety net for developers: it preserves momentum, reduces merge pain, and keeps your history clean. Use messages, apply before pop when unsure, and branch off stashes for ongoing work.<\/p>\n\n\n\n<p>Building and testing on staging branches like those supported on YouStable\u2019s Git friendly hosting, helps you ship confidently without losing a line of code.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Git stash temporarily shelves your uncommitted changes so you can switch branches, pull updates, or run tests on a clean [&hellip;]<\/p>\n","protected":false},"author":21,"featured_media":17865,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[350],"tags":[],"class_list":["post-17352","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-knowledgebase"],"acf":[],"featured_image_src":"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/01\/Git-Stash-Command-Explained-With-Simple-Examples.jpg","author_info":{"display_name":"Sanjeet Chauhan","author_link":"https:\/\/www.youstable.com\/blog\/author\/sanjeet"},"_links":{"self":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts\/17352","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/users\/21"}],"replies":[{"embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/comments?post=17352"}],"version-history":[{"count":7,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts\/17352\/revisions"}],"predecessor-version":[{"id":17778,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts\/17352\/revisions\/17778"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/media\/17865"}],"wp:attachment":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/media?parent=17352"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/categories?post=17352"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/tags?post=17352"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}