Add support for `git stash`

[rowanj]

Should display the list (stack?) of git stash objects that are available, and interfaces to create/apply them

[pipelineoptika]

Looking at the manual, stashes are always pushed to the end of the list, but can be popped (or applied -- no removal) from any stash in the list.

It can be used as a stack by issuing only git stash and git stash pop commands, but it's most certainly a list or queue implementation.

In terms of supported features, we should probably support:

• save
• list (implicit in the UI display - lefthand frame display?)
• show (also implicit in the UI - review in top half of main window?)
• pop (from dropdown on stash item in lefthand list?)
• apply (ditto)
• drop (ditto)
• clear (from dropdown on overall stash list header in lefthand frame?)

[rowanj]

The major feature of this that I had in mind doesn't need much of an interface at all; when an operation (i.e. pull) fails because of local changes, provide a button to "Stash and retry"

[pipelineoptika]

Roger that.

Query: looking at libgit2, I can't quite figure out what the status of git stash support is. Is it that stash is simply another index and set of objects that one can access with the existing set of APIs under libgit2?

[pipelineoptika]

A button on the failure dialog, or similar?

On 06/01/2012, at 3:26 PM, Rowan Jamesreply@reply.github.com wrote:

The major feature of this that I had in mind doesn't need much of an interface at all; when an operation (i.e. pull) fails because of local changes, provide a button to "Stash and re-try"

---

Reply to this email directly or view it on GitHub:
#14 (comment)

[rowanj]

Yeah, that was the idea. The current workaround is to command-line stash it or actually commit it and ammend/rebase that out after the fact.

[RomainMuller]

I second that request. I would like to see all existing stashes of my repos right below the "branches" list. Being able to drop them from context menu is probably good as well. In my opinion, save, pop, apply are not priorities as long as the visibility is there. Also, from my point of view, a dropdown for stashes wouldn't be any improvement over using CLI (too many clicks involved) - everything should be context-menu available from the lefthand frame.

[killercup]

I would very much like to see this feature. GitX (L) supports this.

[williscool]

+1

You could probably just steal the from GitX (L) here. That part is reasonably quick

[jramsdale]

This was a really nice GitX(L) addition. I may move to gitx-dev anyway, but I'll be sad about losing this feature...

[claytonrcarter]

So maybe I'm being overly ambitious here, but I decided to see if I could port this over from GitX(L) (along w/ a couple other things I like from GitX(L)) and I simply couldn't get this GitX to build. I'm using XCode 4.5.2 on 10.8; I installed CMake, cloned this project from the URL specified, init'ed and updated submodules and ran into a few CMake errors (couldn't find CMakeLists.txt for one) and libgit2 errors (can't find git2/oid.h) and such. I'm still fairly new to XCode, but is the project pretty involved to get up and running to build? Any assistance to get this setup would be great since I have a little time and a lot of desire to being in stash support. Thanks.

[rowanj]

The objective-git submodule itself has submodules (libgit2); did you recursively init them?

I use git submodule update --init --recursive at the top-level GitX directory.

[claytonrcarter]

Thank you, yes, that fixed it. (Along with changing the code signing settings and a build clean.) Of course, now that I got it to build I realize I'm in way over my head. Alot of the changes look like they can be copied between files, but that was too tedious to do manually, and the organizational structure is too different for me to be able to figure out how to do a format-patch | am. Thanks for the help, but sorry I couldn't be more of one.

[rowanj]

Fortunately Git handles moved files pretty well; but yes, some of the changes I've made are quite intrusive to the project structure.

@claytoncarter If you've isolated the changes (and/or the commits they happened in on GitX (L)), that's a long way toward getting it done. Can you list them here easily?

[claytonrcarter]

Keeping in my that I'm in over my head and also very poor in ObjC, here's what it looks like to me:

There were two main efforts to get stashes working. The first happened on a branch starting with SHA 0a3b600 and was merged back after SHA 33e21e2, although it looks like there's a bunch of other stuff in that branch and most of the stash action happened in commits 0a3b600, cc5c93c, be507c8 and cb59e86.

The second effort was done on a branch starting with SHA 2158f1e and was merged into master after SHA ba51ae8.

After that, it looks like there were bug fix commits at b4557eb, 76c0a97, 5fde8e8, 12ca779.

[rjmunro]

+1 to this. It's the biggest feature I miss since moving from GitX (L).