stakwork / stakwork/stakgraph

Local File Indexing

Open
#59 4 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
112
Forks
21
Avg merge
5h 55m
Merged PRs (30d)
115

Description

I have my Git Repo cloned to my local machine, as i work on it, between commits. Is there a way to get it to index the local version of the repo. Instead of pulling it Directly from Git the Whole time.

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 tracing how the repository currently obtains source files from Git and how those files are indexed into the source parser and Neo4j graph. Define the expected local-repository workflow and identify the entry points involved before implementing it. Done means a cloned repository can be indexed from its local working tree without repeatedly pulling from Git.

Written by the indexing model from the issue text.

Assessment

Tech stack
neo4j, typescript
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.