After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 648323 - stash changes command
stash changes command
Status: RESOLVED OBSOLETE
Product: gitg
Classification: Applications
Component: gitg-0.x
git master
Other Linux
: Normal enhancement
: ---
Assigned To: gitg-maint
gitg-maint
Depends on:
Blocks:
 
 
Reported: 2011-04-20 16:46 UTC by Adam Dingle
Modified: 2018-05-22 13:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Adam Dingle 2011-04-20 16:46:35 UTC 
It's nice that gitg offers to stash my changes for me if I try to merge when I have uncommitted changes in my working directory.  It would also be nice if there were an explicit command to stash changes.  In other words, I'd like to be able to right click on my unstaged (or staged) changes in the main gitg view and choose Stash Changes to stash them directly.

Details: of course, stashing works on all uncommitted changes both staged and unstaged.  So if I have both staged and unstaged changes, I could run this command on either one and the effect would be the same: both staged and unstaged changes would be stashed.  We could display a confirmation message prior to stashing which would make this clear.
Comment 1 Sindhu S 2013-06-13 14:24:03 UTC 
As this bug was filed against an older version of gitg, moving bug to gitg-0.x 

Staging, stashing changes and committing changes have not yet been implemented in the current gitg (vala version). 

Marking bug as RESOLVED and OBSOLETE.
Comment 2 Jean-François Fortin Tam 2013-06-20 13:45:44 UTC 
...Then if the feature is not yet implemented in whatever new version you're preparing, by definition the bug is still open.
Comment 3 Sindhu S 2013-06-20 14:53:52 UTC 
(In reply to comment #2)
> ...Then if the feature is not yet implemented in whatever new version you're
> preparing, by definition the bug is still open.

Hi!

Sorry about the messup. We will definitely fix it in the new version and will see to it that the errors reported here don't occur when the same features are implemented in the new vala-version of gitg.

Please see our discussion here: https://mail.gnome.org/archives/gitg-list/2013-June/msg00008.html
Comment 4 GNOME Infrastructure Team 2018-05-22 13:05:50 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gitg/issues/15.