Chan Jun Da

Closing this issue as there have been no recent updates and I believe the original intention of the issue was to have a local repo stored within the reposense repository...

I agree, think we can close the issue

Closed in view of both https://github.com/reposense/RepoSense/pull/1750 and https://github.com/reposense/RepoSense/pull/1647 being merged which puts limits on the file size being analyzed and limits on the number of characters being displayed when viewing...

I believe we can close this issue as the investigation some time back. Reposense works if users already have access to the repo via their own git commands.

I believe we can discuss whether to close this issue or discuss its importance as it is somewhat similar to https://github.com/reposense/RepoSense/issues/1637. Local repositories now use the full path specified as...

I believe the first two points have been addressed by the https://github.com/reposense/RepoSense/pull/1647 and https://github.com/reposense/RepoSense/pull/1750.

Hi, I'm a new contributor here and would like to try my hand at this issue. Can it be assigned to me?

Dropping my two cents, I mostly agree with what @gok99 says. I think we can start with some possible uses of such deep cloning features in testing to see if...

Sounds good to me @sikai00

https://github.com/reposense/RepoSense/issues/1902 Yes, it is a relatively common upstream issue recently I believe.