dsh-git-sidebar：在 DSH 对话页查看 Git 工作区未提交改动
dsh-git-sidebar 是 DeepSeek Harness (DSH) Web GUI 的嵌入式插件，由 H2O-MERO 维护，采用 MIT 许可证。该插件旨在解决用户在对话页处理工作区文件时，需频繁切换终端或 IDE 以查看 Git 状态的高操作成本问题。它在 DSH 对话页右侧提供 VSCode 风格的未提交改动侧边栏，允许用户在不离开当前会话界面的情况下，直观查看当前工作区 Git 仓库的已暂存、未暂存及未跟踪文件。 核心功能包括自动跟随当前对话的工作区仓库，支持查看文件状态徽标（如 M、A、D）、行级差异统计（+/−）及单文件 diff 展开；重命名文件会展示新旧路径，未跟
Read MoreThe Distinction Between Git's Staging Area and Working Directory: The Reason for `add` Before `commit`
This article introduces the core concepts, differences, and functions of the working directory and staging area in Git. The working directory consists of files that can be directly operated on locally (like a draft paper), while the staging area is an internal intermediate repository within Git (like a pending review express box). The key differences between them are as follows: location (the working directory is the local file system, while the staging area is internal to Git), editing methods (the working directory can be modified directly, while the staging area requires changes via commands), Git tracking status (the working directory is untracked, while the staging area is marked for commit), and visibility (modifications in the working directory are directly visible, while the staging area is only visible to Git). The process of "add before commit" is mandatory because the staging area allows for more selective commits: skipping the staging area and directly committing would cause Git to submit all changes in the working directory, potentially leading to accidental commits of incomplete work. By following the workflow of "modify → git status → git add → git commit", developers can achieve staged commits. As a buffer zone, the staging area helps developers flexibly control the scope of commits, preventing drafts or incomplete content from being accidentally committed and making code management more controllable.
Read MoreDetailed Explanation of the Relationships Between Git Working Directory, Staging Area, and Local Repository
The three core areas of Git (working directory, staging area, and local repository) have clear divisions of labor and work together to complete version control. **Working Directory** is the directory you directly operate on (e.g., a project folder), where you can freely modify files (add, delete, edit). It is the "operation site" visible to the user. **Staging Area** is a hidden temporary area (`.git/index`). You use `git add` to stage changes for commit, and you can preview or undo them (e.g., `git reset HEAD <file>`). It acts like a "transfer station/fridge". **Local Repository** is the `.git` directory, which stores project version history, branches, etc. Changes from the staging area are committed into version history via `git commit`, making it a "permanent storage room". The core workflow among the three is: **Modify → Stage → Commit**: Modify files in the working directory, stage them with `git add`, and commit to the local repository with `git commit`. Understanding this workflow allows you to manage code versions clearly and avoid operational chaos.
Read More