blocks|key|2933020|text|git+stash+push有一个选项--keep-index，它可以完全满足您的需求。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2933021|因此，运行git+stash+push+--keep-index。|2933022|entityMap^0|0|E|J|C|0|5|R|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

<code>git stash push</code> has an option <code>--keep-index</code> that does exactly what you need.
So, run <code>git stash push --keep-index</code>.

blocks|key|2933242|text|这可以通过3个步骤来完成:保存暂存的更改，存储其他所有内容，使用暂存的更改恢复索引。这基本上就是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2933243|git+commit+-m+'Save+index'
git+stash+push+-u+-m+'Unstaged+changes+and+untracked+files'
git+reset+--soft+HEAD%5E|code-block|syntax|javascript|2933244|这将完全符合您的要求。|2933245|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

This may be done in 3 steps: save staged changes, stash everything else, restore index with staged changes. Which is basically:

<pre><code>git commit -m 'Save index'
git stash push -u -m 'Unstaged changes and untracked files'
git reset --soft HEAD^
</code></pre>

This will do exactly what you want.

blocks|key|3147850|text|使用git+version+2.7.4，您可以这样做：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3147851|git+stash+save+--patch|code-block|syntax|javascript|3147852|git将询问您是否将更改添加到stash中。|3147853|然后你只需回答y或n|3147854|您可以像往常一样恢复工作目录：|3147855|git+stash+pop|3147856|或者，如果您想将保存的更改保存在stash中：|3147857|git+stash+apply|3147858|entityMap^0|2|H|0|0|0|3|0|7|1|9|1|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1A|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|1B|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|1C|8|@]|D|@]|E|$]]|$1|U|3|V|5|H|7|1D|8|@]|D|@]|E|$I|J]]|$1|W|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|X|$]]

With <code>git version 2.7.4</code> you may do:

<pre><code>git stash save --patch
</code></pre>

The <code>git</code> will ask you to add or not your changes into stash. 
And you then just answer <code>y</code> or <code>n</code>

You can restore working directory as you always do that:

<pre><code>git stash pop
</code></pre>

or, if you want to keep saved changes in stash:

<pre><code>git stash apply
</code></pre>

blocks|key|3147968|text|在Git中只存储工作树(未暂存的更改)比它应该更难。公认的答案是隐藏未暂存的更改，但也会隐藏暂存的更改(并将它们保留为暂存)，这很少是您想要的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3147969|此别名可以很好地工作：|3147970|stash-working+=+"!f()+{+\
++git+commit+--quiet+--no-verify+-m+\"temp+for+stash-working\"+&&+\
++git+stash+push+\"$@\"+&&+\
++git+reset+--quiet+--soft+HEAD~1;+};+f"|code-block|syntax|javascript|3147971|它临时提交暂存的更改，从剩余的更改创建存储(并允许将--include-untracked和--message等其他参数作为别名参数传递)，然后重置临时提交以取回暂存的更改。|offset|length|style|CODE|3147972|它类似于@Simon+Knapp的answer，但有一些细微的区别--它在采取的临时操作中使用--quiet，它接受任意数量的stash+push参数，而不是硬编码-m，并且它确实将--soft添加到最终的重置中，以便索引保持启动时的状态。它还在提交时使用--no-verify，以避免从预提交钩子(HT：@Granfalloner)对工作副本进行更改。|3147973|有关仅存储阶段性更改(别名为stash-index)的相反问题，请参阅this+answer。|3147974|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/60663567/430128|1|https://stackoverflow.com/a/60875067/430128^0|0|0|0|Q|J|1A|9|0|1B|7|1X|4|2A|2|2J|6|3K|B|H|6|0|0|E|B|Z|B|1|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|15|8|@$K|16|L|17|M|N]|$K|18|L|19|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1A|8|@$K|1B|L|1C|M|N]|$K|1D|L|1E|M|N]|$K|1F|L|1G|M|N]|$K|1H|L|1I|M|N]|$K|1J|L|1K|M|N]]|9|@$K|1L|L|1M|1|1N]]|A|$]]|$1|Q|3|R|5|6|7|1O|8|@$K|1P|L|1Q|M|N]]|9|@$K|1R|L|1S|1|1T]]|A|$]]|$1|S|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]|10|$5|V|W|X|A|$Y|11]]]]

Stashing just the working tree (unstaged changes) in Git is more difficult than it should be. The accepted answer stashes the unstaged changes, but also stashes the staged changes (and leaves them staged as well), which is rarely what you want.
This alias works well:
<pre><code>stash-working = &quot;!f() { \
 git commit --quiet --no-verify -m \&quot;temp for stash-working\&quot; &amp;&amp; \
 git stash push \&quot;$@\&quot; &amp;&amp; \
 git reset --quiet --soft HEAD~1; }; f&quot;
</code></pre>
It commits the staged changes temporarily, creates a stash from the remaining changes (and allows additional arguments such as <code>--include-untracked</code> and <code>--message</code> to be passed as alias arguments), and then resets the temporary commit to get back the staged changes.
It is similar to @Simon Knapp's <a href="https://stackoverflow.com/a/60663567/430128">answer</a>, but with a few minor differences -- it uses <code>--quiet</code> on the temporary actions taken, and it accepts any number of parameters for the stash <code>push</code>, rather than hard-coding the <code>-m</code>, and it does add <code>--soft</code> to the final reset so that the index remains as it started. It also uses <code>--no-verify</code> on the commit to avoid changes to the working copy from pre-commit hooks (HT: @Granfalloner).
For the opposite problem of stashing just the staged changes (alias <code>stash-index</code>) see <a href="https://stackoverflow.com/a/60875067/430128">this answer</a>.

blocks|key|3147883|text|要将未标记(未添加到提交)的文件添加到stash，请运行以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3147884|git+stash+-k|code-block|syntax|javascript|3147885|如果您希望将新添加的文件(未暂存-不是绿色的)也包含到存储中，请执行以下操作：|3147886|git+stash+-k+-u|3147887|然后，您可以提交暂存的文件。在此之后，您可以使用以下命令取回最后隐藏的文件：|3147888|git+stash+pop|3147889|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

To add the unstagged (not added to commit) files to stash, run the following command:
<pre><code>git stash -k
</code></pre>
If you want to include newly added files(which is not staged - not in green) also to the stash, do the following:
<pre><code>git stash -k -u
</code></pre>
Then you can commit the staged files. After that you can get back the last stashed files using the command:
<pre><code>git stash pop
</code></pre>

blocks|key|2933304|text|Git没有一个命令来只保存未暂存的更改。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2933305|但是，Git确实允许您指定要隐藏的文件。|2933306|git+stash+push+--message+'Unstaged+changes'+--+app/controllers/products_controller.rb+test/controllers/products_controller_test.rb|code-block|syntax|javascript|2933307|如果您只想在这些文件中隐藏特定的更改，请添加--patch选项。|offset|length|style|CODE|2933308|git+stash+push+--patch+--message+'Unstaged+changes'+--+app/controllers/products_controller.rb+test/controllers/products_controller_test.rb|2933309|--include-untracked选项允许您隐藏未跟踪的文件。|2933310|git+stash+push+--include-untracked+--message+'Untracked+files'+--+app/controllers/widgets_controller.rb+test/controllers/widgets_controller_test.rb|2933311|运行git+help+stash+(或man+git-stash)获取更多信息。|2933312|注意:如果您的未暂存的更改相当无关紧要，那么@alesguzik's+answer可能更容易一些。|2933313|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/29863853/242933^0|0|0|0|M|7|0|0|0|J|0|0|2|E|J|D|0|M|J|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|18|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|19|8|@$K|1A|L|1B|M|N]]|9|@]|A|$]]|$1|O|3|P|5|F|7|1C|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|1D|8|@$K|1E|L|1F|M|N]]|9|@]|A|$]]|$1|S|3|T|5|F|7|1G|8|@]|9|@]|A|$G|H]]|$1|U|3|V|5|6|7|1H|8|@$K|1I|L|1J|M|N]|$K|1K|L|1L|M|N]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1M|8|@]|9|@$K|1N|L|1O|1|1P]]|A|$]]|$1|Y|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]]]

Git doesn't have a command that stashes only your unstaged changes.

Git does, however, let you specify which files you want to stash.

<pre><code>git stash push --message 'Unstaged changes' -- app/controllers/products_controller.rb test/controllers/products_controller_test.rb
</code></pre>

If you only want to stash specific changes in those files, add the <code>--patch</code> option.

<pre><code>git stash push --patch --message 'Unstaged changes' -- app/controllers/products_controller.rb test/controllers/products_controller_test.rb
</code></pre>

The <code>--include-untracked</code> option lets you stash untracked files.

<pre><code>git stash push --include-untracked --message 'Untracked files' -- app/controllers/widgets_controller.rb test/controllers/widgets_controller_test.rb
</code></pre>

Run <code>git help stash</code> (or <code>man git-stash</code>) for more info.

Note: If your unstaged changes are rather disoganized, <a href="https://stackoverflow.com/a/29863853/242933">@alesguzik's answer</a> is probably easier.

blocks|key|3147747|text|扩展前面的答案，我有时会有一组复杂的更改，但希望先提交一个单独的更改。例如，我可能发现了一个bug或其他不正确的代码，我希望在我的阶段性更改之前修复这些代码。一种可能的方法是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3147748|首先隐藏所有内容，但保留暂存的更改|3147749|3147750|+$+git存储存储--保留-索引--包含-未跟踪|blockquote|3147751|3147752|3147753|现在，将分段的更改也单独存储|3147754|3147755|+$+git存储存储|3147756|3147757|3147758|进行修改以修复；并测试；提交它们：|3147759|3147760|+$+git+add+--交互式|3147761|3147762|$+git提交-m“修复...”|3147763|3147764|现在恢复以前暂存的更改：|3147765|3147766|+$+git+stash+pop|3147767|3147768|3147769|解决任何冲突，并注意如果存在冲突，git将应用但不会删除顶级存储条目。|3147770|(...然后提交暂存的更改，并恢复所有其他更改的存储，然后继续...)|3147771|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1D|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|1F|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1I|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|M|3|N|5|G|7|1K|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1N|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|T|3|U|5|G|7|1P|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1R|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1T|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]|$1|12|3|13|5|G|7|1V|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|1W|8|@]|9|@]|A|$]]|$1|15|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|20|8|@]|9|@]|A|$]]]|1B|$]]

Extending previous answers, I sometimes have a complex set of changes staged, but wish to commit a separate change first. For example, I might have spotted a bug or otherwise incorrect code that I'd like to fix ahead of my staged changes. One possible route to take is this:
first stash everything, but leave the staged changes intact
<blockquote>
$ git stash save --keep-index [--include-untracked]
</blockquote>
now stash the staged changes separately too
<blockquote>
$ git stash save
</blockquote>
make changes for fix; and test; commit them:
<blockquote>
$ git add [--interactive] [--patch]
$ git commit -m&quot;fix...&quot;
</blockquote>
now restore the previously staged changes:
<blockquote>
$ git stash pop
</blockquote>
resolve any conflicts, and note that if there were conflicts, git will have applied but not dropped that top stash entry.
(... Then commit the staged changes, and restore the stash of all the other changes, and continue ...)

blocks|key|255128|text|我使用了一个别名，它接受一个字符串作为发送到stash条目的消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|255129|mystash+=+"!f()+{+git+commit+-m+hold+&&+git+stash+push+-m+\"$1\"+&&+git+reset+HEAD%5E;+};+f"|code-block|syntax|javascript|255130|其中：|255131|255132|提交索引中的所有内容，|unordered-list-item|255133|隐藏工作树中更改的内容(当然可以添加-u或-a)，|offset|length|style|CODE|255134|将最后一次提交重置为工作try+(可能需要使用--soft将其保留在索引中)。<代码>H210<代码>F211|255135|255136|entityMap^0|0|0|0|0|0|I|2|L|2|0|N|6|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Z|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|11|8|@]|9|@]|A|$]]|$1|M|3|N|5|L|7|12|8|@$O|13|P|14|Q|R]|$O|15|P|16|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|L|7|17|8|@$O|18|P|19|Q|R]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|W|$]]

I use an an alias, which accepts a string to use as a message to the stash entry.

<pre><code>mystash = "!f() { git commit -m hold &amp;&amp; git stash push -m \"$1\" &amp;&amp; git reset HEAD^; }; f"
</code></pre>

Which:

<ul>
<li>commits everything in the index,</li>
<li>stashes what is changed in the working tree (could of course add <code>-u</code> or <code>-a</code>),</li>
<li>resets the last commit back to the working try (may want to use <code>--soft</code> to keep it in the index).</li>
</ul>

blocks|key|2933200|text|与这个问题相关的另一个提示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2933201|当您使用以下命令有效地隐藏未暂存的更改时|2933202|2933203|+$+git存储存储--keep-index|blockquote|2933204|2933205|2933206|您可能希望为存储提供一条消息，以便当您执行git+stash+list时，可以更清楚地看到您之前存储的内容，特别是如果您通过进一步的保存来执行该存储操作。例如|offset|length|style|CODE|2933207|2933208|+$+git+stash+save+--keep-index“尚未暂存的更改”|2933209|2933210|2933211|(尽管实际上它包含了其他答案中提到的所有更改)。|2933212|例如，上面的后面可能紧跟着：|2933213|2933214|+$+git+stash+save“暂存功能X的更改”|2933215|2933216|2933217|不过，请注意，您不能然后使用|2933218|stash+$+git+stash+apply“|2933219|+@{1}”###✘不能完全满足您的要求|2933220|2933221|2933222|仅恢复未暂存的更改。|2933223|entityMap^0|0|0|0|0|0|0|L|E|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|1I|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1L|8|@$L|1M|M|1N|N|O]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|Q|3|R|5|G|7|1P|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1S|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1T|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]|$1|Z|3|10|5|G|7|1V|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1W|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|15|3|16|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|17|3|18|5|G|7|20|8|@]|9|@]|A|$]]|$1|19|3|-4|5|6|7|21|8|@]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|22|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|23|8|@]|9|@]|A|$]]|$1|1D|3|-4|5|6|7|24|8|@]|9|@]|A|$]]]|1E|$]]

Another tip, related to the question:

When you effectively stash your unstaged changes using

<blockquote>
 $ git stash save --keep-index
</blockquote>

you might wish to give the stash a message, so that when you to do a <code>git stash list</code> it's more obvious what you have stashed before, especially if you follow that stash operation by further saves. For example

<blockquote>
 $ git stash save --keep-index "changes not yet staged"
</blockquote>

(although actually it does contain all the changes as noted in other answers).

For example, the above might be followed immediately by:

<blockquote>
 $ git stash save "staged changes for feature X"
</blockquote>

Beware, though, that you can't then use

<blockquote>
 $ git stash apply "stash@{1}" ### ✘ doesn't quite do what you might want
</blockquote>

to restore just the unstaged changes.

blocks|key|250195|text|这是(在我看来)最好的解决方案，它恰好做到了OP所要求的。它只存储未转移、跟踪的文件，而不会进行不必要的提交，也不会使用--keep-index存储所有更改的文件|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|250196|它列出了所有未暂存的跟踪更改(git+diff+--name-only)，将换行符转换为空格(%7C+tr+'\n'+'+')，并使用git+stash+push存储所有这些文件|250197|git+stash+push+$(git+diff+--name-only+%7C+tr+'\n'+'+')|code-block|syntax|javascript|250198|entityMap^0|1O|C|0|F|K|1B|D|1T|E|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|N|$]]

Here's (in my opinion) the best solution, that does exactly what the OP has asked for. It stashes only the unstaged, tracked files – without an unnecessary commit or stashing all changed files with <code>--keep-index</code>
It lists all the unstaged, tracked changes (<code>git diff --name-only</code>) converts newlines to spaces (<code>| tr '\n' ' '</code>) and stashes all these files using <code>git stash push</code>:
<pre class="lang-sh prettyprint-override"><code>git stash push $(git diff --name-only | tr '\n' ' ')
</code></pre>

I'd like to do the following work flow:

<ol>
<li>Add changes to the stage. </li>
<li>Stash all the other changes that were not staged. </li>
<li>Do some stuff with the things in stage (i.e. build, run tests, etc)</li>
<li>Apply the stash. </li>
</ol>

Is there a way to do step 2?

Example

<pre><code> echo "123" &gt; foo
 git add foo # Assumes this is a git directory
 echo "456" &gt;&gt; foo
 git stash
 cat foo # Should yield 123
</code></pre>

Stashing only un-staged changes in Git

我想做以下工作流程：将更改添加到舞台。隐藏所有其他未暂存的更改。在stage中做一些事情(例如构建、运行测试等)，应用stash。有没有办法完成第二步？示例 echo "123" > foo git add foo # Assumes this is a git directory echo "456" >> foo git stash cat foo # Should yield 123

问仅在Git中存储未暂存的更改
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问仅在Git中存储未暂存的更改EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问仅在Git中存储未暂存的更改
EN