Hello all,
        I just tested this and it works fine.  I do know that TextMate’s File Browser seems to dictate the context of certain commands.  For example, if I have a file selected and try to commit, it will act as if I only want to commit the selected file and will behave accordingly.  If I deselect everything and rerun the same command, it will work as if I want to commit everything below the directory currently shown in the File Browser.  That being said, you might need to check to see if deselecting things or selecting the right things makes this work as you expect.

Take care,

Jeremy Whitlock <jwhitlock@apache.org>
Twitter: whitlockjc

On Jan 8, 2014, at 10:13 AM, Charles Stuart <charles.stuart@gmail.com> wrote:

> Hi,
>
> The “Commit” command in the git bundle no longer works for me.
>
> If I run “Show Uncommitted Changes”, the git bundle properly displays the diff. However, if I run the “Commit” command, it instead displays: "Working directory is clean (nothing to commit)”.
>
> So the repro steps are:
>
> 1. Make a change to a file
> 2. Run `git diff` or “Show Uncommitted Changes” to verify that a change has been made
> 3. Run the “Commit” command
>
> Is anyone else experiencing this issue?
>
> Thanks,
> Charles
>

> _______________________________________________
> textmate mailing list
> textmate@lists.macromates.com
> http://lists.macromates.com/listinfo/textmate


_______________________________________________
textmate mailing list
textmate@lists.macromates.com
http://lists.macromates.com/listinfo/textmate