Feature Request: Option to Initialize Git Repository After Cloning

[bryanprimus]

Feature Request

Is your feature request related to a problem? Please describe.
Currently, when using gitpick to clone files or folders from a remote repository, the downloaded directory is not initialized as a git repository (i.e., there is no .git directory). This differs from the regular git clone behavior and means users who want to track changes or start a new project with version control must manually run git init in the target directory after cloning with gitpick.

Describe the solution you'd like
Add an option or flag (e.g., --init or similar) to the gitpick CLI that automatically initializes the target directory as a new git repository after cloning. This would streamline workflows for users who want to start tracking changes immediately.

Describe alternatives you've considered

• Manually running git init after cloning (current workaround)
• Using scripts to automate the two-step process

Additional context

• This feature would help users quickly scaffold new projects that are version-controlled, without extra manual steps.
• It would also be nice after git init we can assign initial commit to it.
• It would make gitpick even more of a true degit/git clone drop-in for bootstrapping projects.

Thank you for considering this enhancement!

[nrjdalal]

will check on/before this weekend