Current Behaviour
Currently, the engine requires a remote Git URL to fetch and process data. This architecture is great for automation via GitHub Actions, but it limits the ability to analyze local repositories, private projects, or codebases that are not hosted on a public remote.
This feature would allow the engine to accept a local file system path as an input, targeting a directory that has already been cloned or initialized with a Git history.
Proposed Changes
- Update the input parser to detect if the provided argument is a local directory path.
- Bypass the git clone or remote fetch process when a local path is detected.
- Point the analysis engine directly to the local .git directory of the provided path.
- Ensure the path resolution logic handles both relative and absolute paths.
Flagged via user feedback on the r/datavisualization launch thread.
Current Behaviour
Currently, the engine requires a remote Git URL to fetch and process data. This architecture is great for automation via GitHub Actions, but it limits the ability to analyze local repositories, private projects, or codebases that are not hosted on a public remote.
This feature would allow the engine to accept a local file system path as an input, targeting a directory that has already been cloned or initialized with a Git history.
Proposed Changes
Flagged via user feedback on the r/datavisualization launch thread.