Proposal: allow already cloned repo

[aralroca]

For example, I have repos on Bitbucket, even though only Github is supported, which is fine. It would be nice to add the option to generate the txt file of the cloned repos on your machine. Ex:

git2txt .

When . is the pathname

[AlpTalhaYazar]

Hi @aralroca, thanks for opening this issue! This is a valuable enhancement that would make the tool more versatile. I'd like to suggest two possible approaches for discussion:

Approach 1: Using --local flag

# Using a dedicated flag for local repositories
git2txt --local /path/to/local/repo

# Examples:
git2txt --local ./my-project
git2txt --local ~/Projects/my-repo
git2txt --local /Users/developer/Projects/some-repo

Approach 2: Using file:// protocol

# Using Git's URL format
git2txt file:///path/to/local/repo

# Examples:
git2txt file:///./my-project
git2txt file:///home/projects/my-repo
git2txt file:///Users/developer/Projects/some-repo

The --local approach feels more straightforward - you just point it to your folder and it works. It's similar to how many other command line tools work, which makes it pretty intuitive, especially if you're new to the tool.

The file:// approach is interesting because it sticks to how Git itself handles local repos. It might look a bit more technical at first, but it could make it easier to add support for other sources in the future without adding more flags.

Both ways would make the tool faster since we wouldn't need to clone the repo again. I'm curious what others think would feel more natural to use day-to-day? Would love to hear everyone's thoughts on this.

[aralroca]

The flag --local I think makes more sense for me

[MahmoudMabrok]

Is there anyone working on this issue @aralroca @AlpTalhaYazar @addyosmani