Skip to content

Bug Report: Git Commit Message with Spaces Causes Pathspec Parse Error #1691

@DHclly

Description

@DHclly

Description

In DeepSeek TUI v0.8.3, executing git commit --amend -m "feat: message" or git commit -m "feat: message" fails when the message contains spaces (more than one word). Git reports errors like:

error: pathspec 'message' did not match any file(s) known to git
error: pathspec 'feat:' did not match any file(s) known to git

Steps to reproduce

For example:

git commit --amend -m "feat: complete sub-pages"

Results in:

error: pathspec 'sub-pages"' did not match any file(s) known to git

However, the same command works correctly when executed directly in the terminal, indicating this is a DeepSeek TUI issue.

Expected behavior

Image

Actual behavior

Image

Impact

let ai exec git commit

Environment

  • OS: Windows 10
  • DeepSeek CLI version: v0.8.3
  • Install method: release binary
  • Model/provider: MiniMax-M2.7
  • Terminal app: VS Code terminal
  • Shell: PowerShell

Logs, screenshots, or recordings

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingenhancementNew feature or request

    Projects

    Status
    Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions