MateusMolina/obsidian-git-file-explorer

[Feature Request] Per File Git Status and Selective Staging

Open

#22 opened on May 8, 2026

View on GitHub
 (3 comments) (0 reactions) (0 assignees)TypeScript (7 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (25 stars)
PR merge metrics
 (PR metrics pending)

Description

This plugin is as close as it gets to what I was looking for. However, either I haven't figured it out yet or it is not implemented.

The feature I'm missing is a selective display and staging for individual files in the repo.

Currently, all files with changes are just highlighted. It would be nice to have more control per file. I.e., indicate "modified", "untracked", "ignored", ... (e.g., by widgets similar to the repo changes and commit widget, but per file) Additionally, options for basic git commands (e.g., via the context menu) for git-add, and such would be nice. The commit function of the git-widget always adds all new and modified files for the commit. This functionality would be nice to have via a checkbox or setting, to have more control of what is actually committed.

This seems like an easy addition considering the current functionality. But my quick look into the source, revealed I'm not fluent enough with JS to do it them myself.

Contributor guide

Research direction
Explore the plugin's codebase to understand how file statuses (modified, untracked) are currently determined. Look at the existing commit widget and repo changes widget to see how they display statuses. Consider adding per file widgets that show status icons and context menu actions for git add, etc. Check the plugin's API for Obsidian to integrate with the file explorer.
Tech stack
typescript
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Needs maintainer response
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitObsidian plugin development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60