git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git Stash Synchronization - Best Workflow?

From
Brooke Kuhlmann <brooke@alchemists.io>
Date
Sep 6, 2025, 12:50 UTC
Message-ID
<FEB150D4-2B5E-41CF-ADCE-93DD0B48D364@alchemists.io>
In-Reply-To
<7a206ee3-d68b-40fd-8133-79e4c2be7174@gmail.com>
>  That sounds like a bug if you're getting the rejected message above but the ref on the remote is still being updated. I'll try and take a look at that next week.
OK, sounds good.
> You need to pass the name of the ref whose reflog you want to look at, otherwise it defaults to showing the reflog for HEAD. You should be able to see the reflog for you exported stashes.
I gave this a try and every time I use `git reflog refs/stashes/$USER`, I always get a blank response. No errors and no output.
> Let's try and find why the remote update say's it rejected when it isn't and then we can think about the best way to document pushing and pulling exported stashes.
Sounds good. Happy to test more of this when you're ready.
Previous: Phillip WoodNext: Phillip Wood
Message 5 of 9 in “Git Stash Synchronization - Best Workflow?”
  1. Brooke KuhlmannAug 31, 2025
  2. Phillip WoodSep 1, 2025
  3. Brooke KuhlmannSep 1, 2025
  4. Phillip WoodSep 5, 2025
  5. Brooke KuhlmannSep 6, 2025
  6. Phillip WoodSep 10, 2025
  7. Brooke KuhlmannSep 11, 2025
  8. Phillip WoodSep 19, 2025
  9. Brooke KuhlmannSep 19, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.