blocks|key|3297870|text|我会选择第二种方法，尽管我不知道为什么你不能把它提交给master/featured分支。挑选樱桃也是可能的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3297871|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I'd go with second approach although no idea why you can't commit it to master/featured branch . It is possible to do cherry-picking too.

blocks|key|3084453|text|不可能通过fetch或其他方式获取它，镜像refspec是fetch+=+%2Brefs/*:refs/*，即使stash是refs/stash，它也不会被发送。显式的refs/stash:refs/stash也不起作用！|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3084454|这只会让人感到困惑，因为它不会获取所有的存储，只获取最新的存储；存储的列表是引用refs/stashes的引用日志。|BOLD|3084455|entityMap^0|T|M|1O|A|2A|L|0|14|C|1H|4|0^^$0|@$1|2|3|4|5|6|7|K|8|@$9|L|A|M|B|C]|$9|N|A|O|B|C]|$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|H]]|D|@]|E|$]]|$1|I|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|J|$]]

It's not possible to get it via fetch or so, the mirror refspec is <code>fetch = +refs/*:refs/*</code>, and even though stash is <code>refs/stash</code> it doesn't get sent. An explicit <code>refs/stash:refs/stash</code> has no effect either!

It would only be confusing anyway since that wouldn't fetch all stashes, only the latest one; the list of stashes is the reflog of the ref <code>refs/stashes</code>.

blocks|key|327782|text|我参加聚会有点晚了，但我相信我找到了一些对我有用的东西，如果你们的情况相同或相似，也可能对你有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|327783|我正在开发它自己的分支中的一个特性。分支不会合并到master中并被推送，直到它完成，或者我已经提交了我觉得舒服的展示给公众。因此，当我想要将未暂存的更改传输到另一台计算机时，我要做的是：|327784|327785|使用类似于"[non-commit]+FOR+TRANSFER+ONLY“的提交消息进行提交，其中包含您希望通过transfered.|unordered-list-item|offset|length|style|CODE|327786|Login发送到另一台计算机的内容。然后，|327787|执行以下操作：|327788|327789|git+pull+ssh%2Bgit://<username>@<domain>/path/to/project/+rb:lb|327790|如果您以不同的方式访问存储库，则URL可能会有所不同。这将把来自该URL的更改从远程分支"rb“拉到本地分支"lb”。请注意，我有一个运行在我自己的计算机上的ssh服务器，并且能够访问way.|327791|git+reset+HEAD%5E+(暗示--mixed)的存储库。|327792|327793|这会将头重置为指向“非提交”提交之前的状态。|327794|来自git-reset(1)："--mixed：重置索引，但不重置工作树(即，更改的文件将被保留，但不标记为提交)+...“|327795|因此，您最终将对文件进行更改，但不会提交给master，也不需要存储。|327796|但是，这将要求您在进行“非提交”的存储库中执行git+reset+--hard+HEAD%5E操作，因为该提交是垃圾。|327797|entityMap^0|0|0|0|6|U|0|0|0|0|0|1P|0|0|0|F|J|7|0|0|0|G|7|0|0|N|M|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|18|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|1A|8|@$H|1B|I|1C|J|K]]|9|@]|A|$]]|$1|L|3|M|5|G|7|1D|8|@]|9|@]|A|$]]|$1|N|3|O|5|G|7|1E|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1G|8|@$H|1H|I|1I|J|K]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1J|8|@]|9|@]|A|$]]|$1|U|3|V|5|G|7|1K|8|@$H|1L|I|1M|J|K]|$H|1N|I|1O|J|K]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1R|8|@$H|1S|I|1T|J|K]]|9|@]|A|$]]|$1|11|3|12|5|6|7|1U|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|1V|8|@$H|1W|I|1X|J|K]]|9|@]|A|$]]|$1|15|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]]|16|$]]

I'm a little late to the party, but I believe I found something that works for me regarding this and it might for you too if your circumstances are the same or similar.

I'm working on a feature in its own branch. The branch isn't merged into master and pushed until its finished or I've made commits that I feel comfortable showing to the public. So what I do when I want to transfer non-staged changes to another computer is:

<ul>
<li>Make a commit, with a commit message
like "<code>[non-commit] FOR TRANSFER ONLY</code>", featuring the content you want transfered.</li>
<li>Login to the other computer.</li>
<li>Then do:

<code>git pull ssh+git://&lt;username&gt;@&lt;domain&gt;/path/to/project/ rb:lb</code>

The URL might differ for you if you access your repository in a different way. This will pull changes from that URL from the remote branch "rb" into the local branch "lb". Note that I have an ssh server running on my own computer, and am able to access the repository that way.</li>
<li><code>git reset HEAD^</code> (implies <code>--mixed</code>)

This resets the HEAD to point to the state before the "[non-commit]" commit.</li>
</ul>

From git-reset(1):
"<code>--mixed</code>: Resets the index but not the working tree (i.e., the changed files are preserved but not marked for commit) [...]"

So you will have your changes to the files in the end, but no commits are made to master and no need for a stash.

This will however require you to <code>git reset --hard HEAD^</code> in the repository in which you made the "[non-commit]", since that commit is garbage.

blocks|key|3297948|text|注：我刚刚用24小时的git-fu重写了这个答案:)在我的shell历史中，整个shebang现在是三个一行程序。但是，为了您的方便，我对它们进行了解压缩。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3297949|这样，我希望您能够看到我是如何做事情的，而不是盲目地复制/粘贴东西。|3297950|3297951|这是一步一步来的。|3297952|假设是包含存储的~/OLDREPO中的源代码。创建不包含任何存储的测试克隆：|3297953|cd+~/OLDREPO
git+clone+.+/tmp/TEST|code-block|syntax|javascript|3297954|将所有存储推送为临时分支：|3297955|git+send-pack+/tmp/TEST+$(for+sha+in+$(git+rev-list+-g+stash);+\
++++do+echo+$sha:refs/heads/stash_$sha;+done)|3297956|在接收端循环以转换回stashes：|3297957|cd+/tmp/TEST/
for+a+in+$(git+rev-list+--no-walk+--glob='refs/heads/stash_*');+
do+
++++git+checkout+$a+&&+
++++git+reset+HEAD%5E+&&+
++++git+stash+save+"$(git+log+--format='%25s'+-1+HEAD@{1})"
done|3297958|如果你愿意，清理你的临时分支|3297959|git+branch+-D+$(git+branch%7Ccut+-c3-%7Cgrep+%5Estash_)|3297960|做一个git+stash列表，你会得到如下结果：|3297961|stash@{0}:+On+(no+branch):+On+testing:+openmp+import
stash@{1}:+On+(no+branch):+On+testing:+zfsrc
stash@{2}:+On+(no+branch):+WIP+on+sehe:+7006283+fixed+wrong+path+to+binary+in+debianized+init+script+(reported+as+part+of+issue
stash@{3}:+On+(no+branch):+WIP+on+debian-collab:+c5c8037+zfs_pool_alert+should+be+installed+by+default
stash@{4}:+On+(no+branch):+WIP+on+xattrs:+3972694+removed+braindead+leftover+-O0+flag
stash@{5}:+On+(no+branch):+WIP+on+testing:+3972694+removed+braindead+leftover+-O0+flag
stash@{6}:+On+(no+branch):+WIP+on+testing:+db9f77e+fuse_unmount_all+could+be+starved+for+the+mtx+lock
stash@{7}:+On+(no+branch):+WIP+on+xattrs:+db9f77e+fuse_unmount_all+could+be+starved+for+the+mtx+lock
stash@{8}:+On+(no+branch):+WIP+on+testing:+28716d4+fixed+implicit+declaration+of+stat64
stash@{9}:+On+(no+branch):+WIP+on+emmanuel:+bee6660+avoid+unrelated+changes|3297962|在原始存储库上，相同的代码如下所示|3297963|stash@{0}:+WIP+on+emmanuel:+bee6660+avoid+unrelated+changes
stash@{1}:+WIP+on+testing:+28716d4+fixed+implicit+declaration+of+stat64
stash@{2}:+WIP+on+xattrs:+db9f77e+fuse_unmount_all+could+be+starved+for+the+mtx+lock
stash@{3}:+WIP+on+testing:+db9f77e+fuse_unmount_all+could+be+starved+for+the+mtx+lock
stash@{4}:+WIP+on+testing:+3972694+removed+braindead+leftover+-O0+flag
stash@{5}:+WIP+on+xattrs:+3972694+removed+braindead+leftover+-O0+flag
stash@{6}:+WIP+on+debian-collab:+c5c8037+zfs_pool_alert+should+be+installed+by+default
stash@{7}:+WIP+on+sehe:+7006283+fixed+wrong+path+to+binary+in+debianized+init+script+(reported+as+part+of+issue+#57)
stash@{8}:+On+testing:+zfsrc
stash@{9}:+On+testing:+openmp+import|3297964|entityMap^0|0|2|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1D|8|@$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1G|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]|$1|I|3|J|5|6|7|1I|8|@]|D|@]|E|$]]|$1|K|3|L|5|6|7|1J|8|@]|D|@]|E|$]]|$1|M|3|N|5|O|7|1K|8|@]|D|@]|E|$P|Q]]|$1|R|3|S|5|6|7|1L|8|@]|D|@]|E|$]]|$1|T|3|U|5|O|7|1M|8|@]|D|@]|E|$P|Q]]|$1|V|3|W|5|6|7|1N|8|@]|D|@]|E|$]]|$1|X|3|Y|5|O|7|1O|8|@]|D|@]|E|$P|Q]]|$1|Z|3|10|5|6|7|1P|8|@]|D|@]|E|$]]|$1|11|3|12|5|O|7|1Q|8|@]|D|@]|E|$P|Q]]|$1|13|3|14|5|6|7|1R|8|@]|D|@]|E|$]]|$1|15|3|16|5|O|7|1S|8|@]|D|@]|E|$P|Q]]|$1|17|3|18|5|6|7|1T|8|@]|D|@]|E|$]]|$1|19|3|1A|5|O|7|1U|8|@]|D|@]|E|$P|Q]]|$1|1B|3|-4|5|6|7|1V|8|@]|D|@]|E|$]]]|1C|$]]

Note: I've just rewritten this answer with 24 hours more git-fu under my belt :)
In my shell history, the whole shebang is now three one-liners. However, I've uncondensed them for your convenience. 

This way, I hope you will be able to see how I did things, instead of just having to blindly copy/paste stuff.

<hr>

Here is step by step.

Assume is source in ~/OLDREPO containing stashes. Create a TEST clone containing no stashes:

<pre><code>cd ~/OLDREPO
git clone . /tmp/TEST
</code></pre>

Push all the stashes as temp branches:

<pre><code>git send-pack /tmp/TEST $(for sha in $(git rev-list -g stash); \
 do echo $sha:refs/heads/stash_$sha; done)
</code></pre>

Loop on the receiving end to transform back into stashes:

<pre><code>cd /tmp/TEST/
for a in $(git rev-list --no-walk --glob='refs/heads/stash_*'); 
do 
 git checkout $a &amp;&amp; 
 git reset HEAD^ &amp;&amp; 
 git stash save "$(git log --format='%s' -1 HEAD@{1})"
done
</code></pre>

Cleanup your temporary branches if you will

<pre><code>git branch -D $(git branch|cut -c3-|grep ^stash_)
</code></pre>

Do a git stash list and you will something like this:

<pre><code>stash@{0}: On (no branch): On testing: openmp import
stash@{1}: On (no branch): On testing: zfsrc
stash@{2}: On (no branch): WIP on sehe: 7006283 fixed wrong path to binary in debianized init script (reported as part of issue
stash@{3}: On (no branch): WIP on debian-collab: c5c8037 zfs_pool_alert should be installed by default
stash@{4}: On (no branch): WIP on xattrs: 3972694 removed braindead leftover -O0 flag
stash@{5}: On (no branch): WIP on testing: 3972694 removed braindead leftover -O0 flag
stash@{6}: On (no branch): WIP on testing: db9f77e fuse_unmount_all could be starved for the mtx lock
stash@{7}: On (no branch): WIP on xattrs: db9f77e fuse_unmount_all could be starved for the mtx lock
stash@{8}: On (no branch): WIP on testing: 28716d4 fixed implicit declaration of stat64
stash@{9}: On (no branch): WIP on emmanuel: bee6660 avoid unrelated changes
</code></pre>

On the original repository, the same looked like

<pre><code>stash@{0}: WIP on emmanuel: bee6660 avoid unrelated changes
stash@{1}: WIP on testing: 28716d4 fixed implicit declaration of stat64
stash@{2}: WIP on xattrs: db9f77e fuse_unmount_all could be starved for the mtx lock
stash@{3}: WIP on testing: db9f77e fuse_unmount_all could be starved for the mtx lock
stash@{4}: WIP on testing: 3972694 removed braindead leftover -O0 flag
stash@{5}: WIP on xattrs: 3972694 removed braindead leftover -O0 flag
stash@{6}: WIP on debian-collab: c5c8037 zfs_pool_alert should be installed by default
stash@{7}: WIP on sehe: 7006283 fixed wrong path to binary in debianized init script (reported as part of issue #57)
stash@{8}: On testing: zfsrc
stash@{9}: On testing: openmp import
</code></pre>

blocks|key|328787|text|AFAIK+stash的整个想法是将一些不太重要的东西隐藏在当地的地毯下。没有人应该知道你最喜欢的废话;-)唯一的“但是”是:但是如果我在几个工作站上开发呢？那么scp就好多了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|328788|entityMap^0|29|3|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

AFAIK the whole idea of stash is to hide something not-so-important under the local carpet. Nobody should know about your favorite crap ;-) The only "but" is: But if I develop on a couple of workstations? Then <code>scp</code> is way better.

blocks|key|327851|text|有点晚了，但这个答案可能会对某些人有所帮助。我之所以想知道这一点，是因为我想要能够推送正在进行的功能/bug/任何东西，并在另一台计算机上从相同的点工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|327852|对我来说起作用的是提交我正在进行的代码(在我单独工作的分支中)。当我到达我的另一台计算机时，执行一次拉操作，然后使用以下命令撤消提交：|327853|git+reset+--soft+HEAD%5E|code-block|syntax|javascript|327854|继续像以前一样工作，所有正在进行的更改都在那里，未提交和未暂存。|327855|希望能有所帮助。|327856|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

It's a little late, but this answer might help someone. I wanted to know this because I wanted to be able to push an in-progress feature/bug/whatever and work from the same point on another computer.

What works for me is to commit my in-progress code (in a branch that I'm working on alone). When I get to my other computer, do a pull, then undo the commit with: 

<pre><code>git reset --soft HEAD^
</code></pre>

Continue working as you were, with all your in-progress changes there, uncommitted, and unstaged.

Hope it helps.

blocks|key|327862|text|以下代码不适用于存储，但适用于工作目录中未提交的更改。它创建一个分支，自动提交所有当前更改，并推送到远程：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|327863|commit_and_push_+(+)+{
++++#+This+will:
++++#++1.+checkout+a+new+branch+stash-XXX
++++#++2.+commit+the+current+changes+in+that+branch
++++#++3.+push+the+branch+to+the+remote
++++local+locbr=${1:-autostash-XXX}
++++git+checkout+-b+$locbr
++++git+add+.
++++git+commit+-a+-m+"Automatically+created+commit"
++++git+push+origin+$locbr
++++echo+"Autocommitted+changes+in+branch+$locbr+..."
}|code-block|syntax|javascript|327864|像这样使用：|327865|commit_and_push_+my-temp-branch
commit_and_push_|327866|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

The following does not work with the stash, but with the uncommitted changes in the working dir. It creates a branch, autocommits all current changes, and pushes to the remote:

<pre><code>commit_and_push_ ( ) {
 # This will:
 # 1. checkout a new branch stash-XXX
 # 2. commit the current changes in that branch
 # 3. push the branch to the remote
 local locbr=${1:-autostash-XXX}
 git checkout -b $locbr
 git add .
 git commit -a -m "Automatically created commit"
 git push origin $locbr
 echo "Autocommitted changes in branch $locbr ..."
}
</code></pre>

Use like:

<pre><code>commit_and_push_ my-temp-branch
commit_and_push_
</code></pre>

blocks|key|327868|text|似乎有一个非常巧妙的技巧来解决这个问题。您可以使用git+diff+>+file.diff+(并提交文件)，然后使用git+apply+file.diff+(从任何位置)恢复更改，以获得相同的结果。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|327869|here也解释了这一点。|327870|entityMap|0|LINK|mutability|MUTABLE|url|https://superuser.com/a/817350/577906^0|P|K|1M|J|0|0|4|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@]|D|@$9|V|A|W|1|X]]|E|$]]|$1|H|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

There seems to be a very neat trick to solve this. you can use <code>git diff &gt; file.diff</code> (and commit the file) , then restore the changes using <code>git apply file.diff</code> (from anywhere) to achieve the same result.

This was explained <a href="https://superuser.com/a/817350/577906">here</a> as well.

blocks|key|331214|text|我会简单地创建一个新的stash分支，并在不需要该分支时删除该分支。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|331215|在机器1上：|331216|git+add+.+//+Add+work-in-progress+job
git+checkout+-b+stash-branch+//+Create+and+checkout+to+stash-branch
git+commit+-m+'WIP:+job+description'+//+Commit+message
git+push+origin+stash-branch+//+Push+to+remote|code-block|syntax|javascript|331217|在机器2上：|331218|git+pull+origin+stash-branch+//+Pull+the+stash-branch
git+checkout+master+//+Checkout+to+working+branch
git+rebase+stash-branch+//+Rebase+the+stash-branch
git+reset+--soft+//+Equivalent+to+stash!!
git+branch+-d+stash-branch+//+Delete+branch+when+not+needed+from+local
git+push+-d+origin+stash-branch+//+Delete+branch+when+not+needed+from+remote|331219|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I would simply create a new stash branch and the remove whenever that branch is not required.
On Machine 1:
<pre><code>git add . // Add work-in-progress job
git checkout -b stash-branch // Create and checkout to stash-branch
git commit -m 'WIP: job description' // Commit message
git push origin stash-branch // Push to remote
</code></pre>
On Machine 2:
<pre><code>git pull origin stash-branch // Pull the stash-branch
git checkout master // Checkout to working branch
git rebase stash-branch // Rebase the stash-branch
git reset --soft // Equivalent to stash!!
git branch -d stash-branch // Delete branch when not needed from local
git push -d origin stash-branch // Delete branch when not needed from remote
</code></pre>

blocks|key|328878|text|currently+accepted+answer在技术上是正确的，你不能直接告诉Git将你所有的存储推送到遥控器上，然后将所有东西都拉到另一台计算机上的本地存储中。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|328879|虽然currently+top-upvoted+answer应该可以工作，但我不喜欢它创建一堆临时分支，并且它需要手动检查存储提交并将其保存为存储，这可能会导致this+comment+mentioned等问题，并导致重复的On+(no+branch):+On+testing:。当然，一定有更好的方法！|style|CODE|328880|因此，虽然不能直接推送stash，但stash只是一次提交(实际上是两次提交)，并且根据git+push手册页，您可以推送提交：|328881|表达式通常是您想要推送的分支的名称，但它可以是任意的"SHA-1+<src>“...|328882|328883|我选择将存储推送到refs/stashes/*，这样我就不会用多余的树枝弄乱我的遥控器。所以我可以这样做：|328884|git+push+origin+stash@{0}:refs/stashes/$(git+rev-parse+--short+stash@{0})|code-block|syntax|javascript|328885|(+rev-parse命令获取存储的短散列，它对于存储库是唯一的。)|328886|下一步，我需要从另一台计算机取回藏匿的东西。默认情况下，Git只获取分支，所以我需要专门获取存储：|328887|git+fetch+origin+refs/stashes/*:refs/stashes/*|328888|现在要将存储提交转换回实际的存储。如前所述，虽然我可以像往常一样检查存储提交、重置和存储，但我不喜欢它需要额外的步骤，或者它可能不维护存储的索引状态。我在网上寻找一种自动实现这一点的方法，但是我的搜索失败了。最后，我浏览了git+stash的手册页，在那里我找到了以下内容：|328889|328890|创建|blockquote|328891|328892|创建一个stash+(这是一个常规的提交对象)并返回其对象名，而不将其存储在ref名称空间中的任何位置。这是为了对脚本有用。这可能不是您要使用的命令；请参阅上面的“保存”。|328893|商店|328894|将通过git+stash+create+(这是一个悬空的合并提交)创建的给定stash存储在stash+ref中，更新stash+reflog。这是为了对脚本有用。这可能不是您要使用的命令；请参阅上面的“保存”。|328895|328896|因为我已经有了提交，所以store听起来就是我想要的。所以我可以这样做：|328897|git+stash+store+--message+"$(git+show+--no-patch+--format=format:%25s+<SHA>)"+<SHA>|328898|将<SHA>替换为刚刚获取的存储。|328899|(+git+show命令从存储提交中获取提交消息，以用作存储日志的消息。)|328900|在我的本地repo中，存储现在显示为正常：|328901|$+git+stash+list
stash@{0}:+On+master:+temp
...|328902|要清理遥控器，可以像这样从遥控器中删除存储：|328903|git+push+origin+:refs/stashes/<SHA>|328904|此方法还具有幂等的优点:如果再次运行push命令，它将报告Everything+up-to-date。还可以安全地重复运行fetch命令。虽然如果与最新的存储相同，stash+store将跳过存储，但它不能防止旧存储的重复。不过，这是可以解决的，就像我在git-rstash脚本中所做的那样，请参见下面的内容。|328905|328906|为了完成，您还可以轻松地推送所有存储(使用bash)：|328907|for+i+in+$(seq+0+$(expr+$(git+rev-list+--walk-reflogs+--count+stash)+-+1))
do
++git+push+origin+stash@{$i}:refs/stashes/$(git+rev-parse+--short+stash@{$i})
done|328908|或者导入所有获取的存储：|328909|for+stash+in+$(ls+.git/refs/stashes)
do
++git+stash+store+--message+"$(git+show+--no-patch+--format=format:%25s+$stash)"+$stash
done|328910|我已经创建了一个可以作为子命令调用的bash脚本(例如git+rstash+push+0)，所以我不必记住所有这些。git-rstash+can+be+found+here.|328911|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/1550400/2747593|1|https://stackoverflow.com/a/5248758/2747593|2|https://stackoverflow.com/questions/1550378/is-it-possible-to-push-a-git-stash-to-a-remote-repository#comment18835155_5248758|3|/questions/tagged/bash|4|5|https://github.com/501st-alpha1/git-rstash^0|0|P|0|0|34|R|2|S|1|28|M|2|0|18|8|0|X|5|0|0|9|E|0|0|2|9|0|0|0|33|9|0|0|0|0|0|0|0|0|C|5|0|0|1|5|0|2|8|0|0|0|0|0|I|4|T|L|1P|5|2A|B|3J|A|0|0|L|4|3|0|0|0|0|R|H|1M|A|I|4|4|1M|T|5|0^^$0|@$1|2|3|4|5|6|7|2N|8|@]|9|@$A|2O|B|2P|1|2Q]]|C|$]]|$1|D|3|E|5|6|7|2R|8|@$A|2S|B|2T|F|G]]|9|@$A|2U|B|2V|1|2W]|$A|2X|B|2Y|1|2Z]]|C|$]]|$1|H|3|I|5|6|7|30|8|@$A|31|B|32|F|G]]|9|@]|C|$]]|$1|J|3|K|5|6|7|33|8|@$A|34|B|35|F|G]]|9|@]|C|$]]|$1|L|3|-4|5|6|7|36|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|37|8|@$A|38|B|39|F|G]]|9|@]|C|$]]|$1|O|3|P|5|Q|7|3A|8|@]|9|@]|C|$R|S]]|$1|T|3|U|5|6|7|3B|8|@$A|3C|B|3D|F|G]]|9|@]|C|$]]|$1|V|3|W|5|6|7|3E|8|@]|9|@]|C|$]]|$1|X|3|Y|5|Q|7|3F|8|@]|9|@]|C|$R|S]]|$1|Z|3|10|5|6|7|3G|8|@$A|3H|B|3I|F|G]]|9|@]|C|$]]|$1|11|3|-4|5|6|7|3J|8|@]|9|@]|C|$]]|$1|12|3|13|5|14|7|3K|8|@]|9|@]|C|$]]|$1|15|3|-4|5|6|7|3L|8|@]|9|@]|C|$]]|$1|16|3|17|5|6|7|3M|8|@]|9|@]|C|$]]|$1|18|3|19|5|6|7|3N|8|@]|9|@]|C|$]]|$1|1A|3|1B|5|6|7|3O|8|@]|9|@]|C|$]]|$1|1C|3|-4|5|6|7|3P|8|@]|9|@]|C|$]]|$1|1D|3|1E|5|6|7|3Q|8|@$A|3R|B|3S|F|G]]|9|@]|C|$]]|$1|1F|3|1G|5|Q|7|3T|8|@]|9|@]|C|$R|S]]|$1|1H|3|1I|5|6|7|3U|8|@$A|3V|B|3W|F|G]]|9|@]|C|$]]|$1|1J|3|1K|5|6|7|3X|8|@$A|3Y|B|3Z|F|G]]|9|@]|C|$]]|$1|1L|3|1M|5|6|7|40|8|@]|9|@]|C|$]]|$1|1N|3|1O|5|Q|7|41|8|@]|9|@]|C|$R|S]]|$1|1P|3|1Q|5|6|7|42|8|@]|9|@]|C|$]]|$1|1R|3|1S|5|Q|7|43|8|@]|9|@]|C|$R|S]]|$1|1T|3|1U|5|6|7|44|8|@$A|45|B|46|F|G]|$A|47|B|48|F|G]|$A|49|B|4A|F|G]|$A|4B|B|4C|F|G]|$A|4D|B|4E|F|G]]|9|@]|C|$]]|$1|1V|3|-4|5|6|7|4F|8|@]|9|@]|C|$]]|$1|1W|3|1X|5|6|7|4G|8|@]|9|@$A|4H|B|4I|1|4J]]|C|$]]|$1|1Y|3|1Z|5|Q|7|4K|8|@]|9|@]|C|$R|S]]|$1|20|3|21|5|6|7|4L|8|@]|9|@]|C|$]]|$1|22|3|23|5|Q|7|4M|8|@]|9|@]|C|$R|S]]|$1|24|3|25|5|6|7|4N|8|@$A|4O|B|4P|F|G]|$A|4Q|B|4R|F|G]]|9|@$A|4S|B|4T|1|4U]|$A|4V|B|4W|1|4X]]|C|$]]|$1|26|3|-4|5|6|7|4Y|8|@]|9|@]|C|$]]]|27|$28|$5|29|2A|2B|C|$2C|2D]]|2E|$5|29|2A|2B|C|$2C|2F]]|2G|$5|29|2A|2B|C|$2C|2H]]|2I|$5|29|2A|2B|C|$2C|2J]]|2K|$5|29|2A|2B|C|$2C|2J]]|2L|$5|29|2A|2B|C|$2C|2M]]]]

The <a href="https://stackoverflow.com/a/1550400/2747593">currently accepted answer</a> is technically correct, you can't directly tell Git to push all your stashes to a remote, and then pull everything into your local stashes on another computer.

And while the <a href="https://stackoverflow.com/a/5248758/2747593">currently top-upvoted answer</a> should work, I didn't like that it creates a bunch of temporary branches, and that it requires manually checking out the stash commit and saving it as a stash, which can lead to issues like <a href="https://stackoverflow.com/questions/1550378/is-it-possible-to-push-a-git-stash-to-a-remote-repository#comment18835155_5248758">this comment mentioned</a>, and leads to a duplicate <code>On (no branch): On testing:</code>. Surely there must be a better way!

So while you can't directly push stashes, a stash is just a commit (actually two commits), and per the <code>git push</code> man page you can push commits:

<blockquote>
 The <code>&lt;src&gt;</code> is often the name of the branch you would want to push, but it can be any arbitrary "SHA-1 expression"...
</blockquote>

I chose to push the stashes to <code>refs/stashes/*</code> so that I wouldn't clutter up my remote with extra branches. So I can do that with:

<pre><code>git push origin stash@{0}:refs/stashes/$(git rev-parse --short stash@{0})
</code></pre>

(The <code>rev-parse</code> command gets the short hash of the stash, which will be unique for the repo.)

Next, I need to fetch the stash from the other computer. Git only fetches branches by default, so I need to fetch the stashes specifically:

<pre><code>git fetch origin refs/stashes/*:refs/stashes/*
</code></pre>

Now to convert the stash commit back into an actual stash. As mentioned, while I could just check out the stash commit, reset, and stash as usual, I don't like that it requires extra steps, or that it might not maintain the index state for the stash. I was looking online for a way to do that automatically, but my search-fu failed me. Finally I looked through the man page for <code>git stash</code>, where I found this:

<blockquote>
 create 
 Create a stash (which is a regular commit object) and return its object name, without storing it anywhere in the ref namespace. This is intended to be useful for scripts. It is probably not the command you want to use; see "save" above.
 
 store 
 Store a given stash created via git stash create (which is a dangling merge commit) in the stash ref, updating the stash reflog. This is intended to be useful for scripts. It is probably not the command you want to use; see "save" above.
</blockquote>

Since I already have the commit, <code>store</code> sounds like what I want. So I can do:

<pre><code>git stash store --message "$(git show --no-patch --format=format:%s &lt;SHA&gt;)" &lt;SHA&gt;
</code></pre>

Replacing <code>&lt;SHA&gt;</code> with the stash that was just fetched.

(The <code>git show</code> command gets the commit message from the stash commit, to use as the message for the stash log.)

The stash now shows up as normal in my local repo:

<pre><code>$ git stash list
stash@{0}: On master: temp
...
</code></pre>

To clean up the remote, the stashes can be deleted from the remote like so:

<pre><code>git push origin :refs/stashes/&lt;SHA&gt;
</code></pre>

This method also has the benefit of being idempotent: if you run the <code>push</code> command again, it will report <code>Everything up-to-date</code>. The <code>fetch</code> command can also be safely run repeatedly. While the <code>stash store</code> will skip storing the stash if it is the same as the most recent stash, it doesn't prevent duplicates of older stashes. This can be worked around though, as I do in my <code>git-rstash</code> script, see below.

<hr>

For completion, you can also easily push all stashes (with <a href="/questions/tagged/bash" class="post-tag" title="show questions tagged &#39;bash&#39;" rel="tag">bash</a>):

<pre><code>for i in $(seq 0 $(expr $(git rev-list --walk-reflogs --count stash) - 1))
do
 git push origin stash@{$i}:refs/stashes/$(git rev-parse --short stash@{$i})
done
</code></pre>

or import all fetched stashes:

<pre><code>for stash in $(ls .git/refs/stashes)
do
 git stash store --message "$(git show --no-patch --format=format:%s $stash)" $stash
done
</code></pre>

I've created a <a href="/questions/tagged/bash" class="post-tag" title="show questions tagged &#39;bash&#39;" rel="tag">bash</a> script that can be called as a subcommand (e.g. <code>git rstash push 0</code>) so I don't have to remember all this. <a href="https://github.com/501st-alpha1/git-rstash" rel="noreferrer"><code>git-rstash</code> can be found here.</a>

blocks|key|3084726|text|基于其他答案，如果您在GitHub这样的平台上有一个公共存储库，但不希望正在进行的更改是公共的，那么您可以创建一个私有存储库并将其添加为远程存储库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3084727|要同步更改:提交、推送到专用遥控器上的分支、拉动目标设备，然后执行软/混合重置。|3084728|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Building on other answers, if you have a public repository on a platform like GitHub, but don't want your in-progress changes to be public, you can create a private repository and add it as a remote.
To sync changes: commit, push to a branch on the private remote, pull on the target device, and do a soft/mixed reset.

blocks|key|327943|text|我将混合上面的两个答案，只是为了分享我是如何使用zsh+shell做到这一点的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|327944|非常感谢@Scott+Weldon+(answer-link)和@sehe+(answer-link)对这个问题的回答！我从他们身上学到了很多！多亏了这个问题，我还广泛地学习了shell脚本！|327945|327946|代码的作用非常简单的解释|327947|请参考上面的答案链接，以便更好地(推荐)理解。|327948|代码的作用：|327949|Stash+goes+from+Machine+1+-->+to+remote+-->+to+Machine+2|code-block|syntax|javascript|327950|机器1上的步骤：|327951|1.+Push+the+stash+to+remote+(using+for+loop+for+multiple+stashes)|327952|机器2上的步骤：|327953|1.+Check+stash(es)+in+remote.+(This+is+just+to+check+whether+there+are++previous+stashes+in+remote.+If+there+are,+you+must+delete+them+if+you+don't+want+them+in+you+stash+list.+Command+for+deleting+remote+stashes+are+given+in+bonus)
2.+Fetch+the+stash(es)+to+a+local+ref+folder+named+"ref/stashes"+in+your+.git+folder+in+your+local+repository.+(Its+like+downloading+the+stashes+on+your+PC)
3.+Convert+the+fetched+stash(es)+to+proper+data.+(Its+like+extracting+or+installing+the+stashes+on+your+PC)|327954|奖励：|327955|1.+Check+stash(es)+in+remote
2.+Delete+stash(es)+from+remote+|327956|327957|代码：|327958|在机器1上：|327959|1.+git+push+origin+$(for+sha+in+$(git+rev-list+-g+stash);+do+echo+$sha:"refs/stashes/$(git+rev-parse+--short+$sha)";+done)|327960|在机器2上：|327961|1.+git+ls-remote
2.+git+fetch+origin+"refs/stashes/*":"refs/stashes/*"
3.+for+sha+in+$(git+rev-list+--no-walk+--reverse+--glob='refs/stashes/*');+do+git+stash+store+--message+"$(git+show+--no-patch+--format=format:%25s+$sha)"+$sha;+done|327962|327963|1.+git+ls-remote
2.+git+push+origin+:refs/stashes/<stashFile-1>+:refs/stashes/<stashFile-2>|327964|上面的代码用于多个仓库，也可以用于一个仓库。只需确保您的远程ref/stashes文件夹在本地存储库中只包含您想要的存储。|CODE|327965|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/61356308/9511010|1|https://stackoverflow.com/a/5248758/9511010^0|O|9|0|I|D|0|12|D|1|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|U|B|0^^$0|@$1|2|3|4|5|6|7|1W|8|@$9|1X|A|1Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1Z|8|@]|D|@$9|20|A|21|1|22]|$9|23|A|24|1|25]]|E|$]]|$1|H|3|-4|5|6|7|26|8|@]|D|@]|E|$]]|$1|I|3|J|5|6|7|27|8|@]|D|@]|E|$]]|$1|K|3|L|5|6|7|28|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|29|8|@]|D|@]|E|$]]|$1|O|3|P|5|Q|7|2A|8|@]|D|@]|E|$R|S]]|$1|T|3|U|5|6|7|2B|8|@]|D|@]|E|$]]|$1|V|3|W|5|Q|7|2C|8|@]|D|@]|E|$R|S]]|$1|X|3|Y|5|6|7|2D|8|@]|D|@]|E|$]]|$1|Z|3|10|5|Q|7|2E|8|@]|D|@]|E|$R|S]]|$1|11|3|12|5|6|7|2F|8|@]|D|@]|E|$]]|$1|13|3|14|5|Q|7|2G|8|@]|D|@]|E|$R|S]]|$1|15|3|-4|5|6|7|2H|8|@]|D|@]|E|$]]|$1|16|3|17|5|6|7|2I|8|@]|D|@]|E|$]]|$1|18|3|19|5|6|7|2J|8|@]|D|@]|E|$]]|$1|1A|3|1B|5|Q|7|2K|8|@]|D|@]|E|$R|S]]|$1|1C|3|1D|5|6|7|2L|8|@]|D|@]|E|$]]|$1|1E|3|1F|5|Q|7|2M|8|@]|D|@]|E|$R|S]]|$1|1G|3|12|5|6|7|2N|8|@]|D|@]|E|$]]|$1|1H|3|1I|5|Q|7|2O|8|@]|D|@]|E|$R|S]]|$1|1J|3|1K|5|6|7|2P|8|@$9|2Q|A|2R|B|1L]]|D|@]|E|$]]|$1|1M|3|-4|5|6|7|2S|8|@]|D|@]|E|$]]]|1N|$1O|$5|1P|1Q|1R|E|$1S|1T]]|1U|$5|1P|1Q|1R|E|$1S|1V]]]]

I am going to mix 2 answers from above just to share how I do it with zsh shell.
A huge thanks to @Scott Weldon <a href="https://stackoverflow.com/a/61356308/9511010">(answer-link)</a> and @sehe <a href="https://stackoverflow.com/a/5248758/9511010">(answer-link)</a> for their answers to this question! I learned a lot from them!! Also I learned about shell scripting extensively thanks to this problem!
<hr />
<h2>A very simple explanation of what the codes does</h2>
Please refer to above answer-links for better (recommended) understanding.:
What the code does:
<pre><code>Stash goes from Machine 1 --&gt; to remote --&gt; to Machine 2
</code></pre>
Steps On Machine 1:
<pre><code>1. Push the stash to remote (using for loop for multiple stashes)
</code></pre>
Steps On Machine 2:
<pre><code>1. Check stash(es) in remote. (This is just to check whether there are previous stashes in remote. If there are, you must delete them if you don't want them in you stash list. Command for deleting remote stashes are given in bonus)
2. Fetch the stash(es) to a local ref folder named &quot;ref/stashes&quot; in your .git folder in your local repository. (Its like downloading the stashes on your PC)
3. Convert the fetched stash(es) to proper data. (Its like extracting or installing the stashes on your PC)
</code></pre>
bonus:
<pre><code>1. Check stash(es) in remote
2. Delete stash(es) from remote 
</code></pre>
<hr />
<h2>Codes:</h2>
On Machine 1:
<pre><code>1. git push origin $(for sha in $(git rev-list -g stash); do echo $sha:&quot;refs/stashes/$(git rev-parse --short $sha)&quot;; done)
</code></pre>
On Machine 2:
<pre><code>1. git ls-remote
2. git fetch origin &quot;refs/stashes/*&quot;:&quot;refs/stashes/*&quot;
3. for sha in $(git rev-list --no-walk --reverse --glob='refs/stashes/*'); do git stash store --message &quot;$(git show --no-patch --format=format:%s $sha)&quot; $sha; done
</code></pre>
bonus:
<pre><code>1. git ls-remote
2. git push origin :refs/stashes/&lt;stashFile-1&gt; :refs/stashes/&lt;stashFile-2&gt;
</code></pre>
The above codes are for multiple stashes and can be used for one stash too. Just make sure that your remote <code>ref/stashes</code> folder has only the stashes you want in your local repo.

In git, is it possible to create a stash, push the stash to a remote repository, retrieve the stash on another computer, and apply the stash? 

Or are my options:

<ul>
<li>Create a patch and copy the patch to the other computer, or</li>
<li>Create a minor branch and commit the incomplete work to that branch?</li>
</ul>

Is it possible to push a git stash to a remote repository?

服务器

GitHub

在git中，可以创建一个存储，将该存储推送到远程存储库，在另一台计算机上检索该存储，然后应用该存储吗？或者是我的选择：创建一个修补程序并将该修补程序复制到另一台计算机，或者创建一个次要分支并将未完成的工作提交给该分支-

问可以将git stash推送到远程存储库吗？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问可以将git stash推送到远程存储库吗？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问可以将git stash推送到远程存储库吗？
EN