Concept question about push/pull stashes
From: <hidden>
Date: 2021-09-01 07:44:31
Hello, my question has to goals. I want to understand the design decisions behind a (missing) feature and and wan't to explore the needs of other users before I start to implement something. There is no usual way to exchange stashes with other repos/users. Stashes are code snippets that are unfinished and not clean enough to commit them anywhere not even in another branch. Why? What is the concept behind this? I am sure this was well thought. I just try to understand. A feature like this is often asked by users when you asked the search engine of your trust. One workaround is to simply commit the stashed code, push/pull it, checkoutit into the other repo and delete the last commit. The other workaround is to create a patch-file from a stash. But then the question is how to exchange this file? Why not use the git infrastructure itself? I have workaround in my mind. I couuld use a script wich creates patch files for each existing stash and commit them into the repo. Thats all. To keep the repo "clean" the path files could be archived into a hidden (dotted filed) tar file. Or the tar file could be stored inside the ".git" folder if there is a way. I am interested in your thoughts about this.