mblode / mblode/diffhub

I tried it, here are some wishes

Open
#23 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
22
Forks
4
Avg merge
9h 2m
Merged PRs (30d)
3

Description

I often edit multipe git repos in parallel. I run diffhub multiple times, thats fine.

As long as there is not changes, I'm not able to see which diffhub panel shows which git repo. I kind of want to see what git repo it's tracking and likely also in what folder it is on my local machine.

Also for some reason I had to force reload in the browser panel to catch up with the changes. I often don't create a branch but just work on the main branch and do a 2 line change or so.

Also I just created a new file which did not show up in diffhub (because it's not added in git). Was also confusing, I had to run git status manually and I saw a new file was created. May also show somehow to "show" new files - not in .gitignore

Really like this!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by separating the requested behavior into repository identification, change refresh, and untracked-file visibility. The issue names no files, tests, or entry points, so first locate the code that builds diffhub panels and reads Git state; done would make each panel identifiable, reflect changes without a forced reload, and show non-ignored new files.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, typescript
Domain
cli, developer-experience, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.