{"thread":{"id":"47945","subject":"[FEATURE] git-gui: Staging path(s) should re-select a new path in \"Unstaged Changes\"","startedAt":"2018-02-28T12:59:31Z","lastAt":"2018-02-28T12:59:31Z","messageCount":1,"participants":["Birger Skogeng Pedersen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"340559","messageId":"CAGr--=Jgk==eQ4H8hiOU5x_P53gugXStORkFfTH6iPUrm43VRQ@mail.gmail.com","threadId":"47945","inReplyTo":null,"subject":"[FEATURE] git-gui: Staging path(s) should re-select a new path in \"Unstaged Changes\"","fromName":"Birger Skogeng Pedersen","fromEmail":"birgersp@gmail.com","sentAt":"2018-02-28T12:59:24Z","receivedAt":"2018-02-28T12:59:31Z","isPatch":false,"sender":{"key":"birgersp@gmail.com","avatar":"https://avatars.githubusercontent.com/u/5260237?v=4"},"body":"When a path is selected in \"Unstaged Changes\", it can be staged\n(obviously). When it is staged, the path goes to the \"Staged Changes\"\nlist, and no (new) path is selected. I propose that this action should\nre-select a new path, from the list of paths in \"Unstaged Changes\".\n\nSteps to reproduce (in git-gui):\n1. Open git-gui in a repository which has two or more uncommited, changed files.\n2. Select a path in the list of \"Unstaged Changes\"\n3. Click CTRL/CMD+T to stage the file.\n4. Observe how no (new) path is selected, forcing you to re-select\nanother path if you want to stage it.\n"}]}