Reuse one GitService per project instead of building one per IPC call
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 51/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- electron, git, typescript
- Domain
- desktop, performance
Research direction
Start with src/main/index.ts:117-121 and trace how git() creates GitService and how status refreshes are triggered. Then inspect GitService and its filter-list loading; the proposal is to reuse a service per project path and refresh filters when .git/config changes or periodically. Done means repeated IPC calls reuse the service without leaving filter data stale.
Written by the indexing model from the issue text.
Description
Suggestion from the 2026-10-07 code review (not a bug).
git() in src/main/index.ts:117-121 creates a new GitService for every IPC call. Each one runs an extra git config to list the repository's filter drivers, and a single status() spawns 4–6 git processes. The status refreshes on project open, after every agent run and on panel actions.
Proposal
Cache the service per project path and refresh the filter list when .git/config changes (mtime check), or at most every few seconds.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 2
- Avg merge
- 5h 28m
- Merged PRs (30d)
- 24
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PierrunoYT/patch
-
Claude Code chats: tool calls made inside Claude Code subagents leave cards that end as "(stopped)"Openbug priority: low severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
PierrunoYT/patch#289 ·
Maintainers usually reply within 1 day
-
bug priority: medium severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PierrunoYT/patch#285 ·
Maintainers usually reply within 1 day
-
priority: medium security severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
PierrunoYT/patch#283 ·
Maintainers usually reply within 1 day
-
enhancement priority: medium security severity: medium
Difficulty 5/5 Over a week Newbie friendliness 35/100
PierrunoYT/patch#294 ·
Maintainers usually reply within 1 day
-
priority: low security severity: low
Difficulty 4/5 1-2 days Newbie friendliness 38/100
PierrunoYT/patch#293 ·
Maintainers usually reply within 1 day
All issues in PierrunoYT/patch
Similar issues
-
by: ai-assisted frontend good-for: new-member spike
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Northeastern-Electric-Racing/Argos#847 ·
Maintainers usually reply within 4 days
-
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
SignalK/freeboard-sk#990 ·
Maintainers usually reply within 1 day
-
[missing-inheritance] audit review (1 preset)Possibly taken @github-actions claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
osmberlin/tagging-schema-browser#363 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Albert-Weasker/niubigeo#205 ·
Maintainers usually reply within 1 day
-
area/frontend area/v2 kind/bug priority/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
kubeflow/notebooks#1498 · 1 comment ·
Maintainers usually reply within 1 day