git2txt

Fixes #13 Changes Added new function to handle all GitHub URL formats consistently: HTTPS URLs (e.g., ) SSH URLs (e.g., ) Short format (e.g., ) Added debug logging to help users understand URL processing Fixed trailing slash and .git suffix handling Testing The fix has been tested with all supported URL formats: 1. HTTPS URL: 2. Short format: 3. SSH URL: ```bash git2txt git@github.com:username/

Description The tool sometimes generates incorrect output filenames when processing certain GitHub repository URL formats. This happens because the repository name extraction logic doesn't handle all URL formats consistently. Steps to Reproduce 1. Run the tool with a GitHub URL ending in a slash: Expected: Output file named Actual: Output file named 2. Run the tool with a short format URL: Expected: Output file named Actual: Output file named (works correctly) 3. Run the tool with an SSH URL: Expected: Output file named Actual: Output file named (missing .txt extension) Impact Users get unexpected output filenames Some formats result in files without the .txt extension URLs with trailing slashes create files named just

This PR introduces a new feature that allows users to export a Git repository at a specific commit version. Previously, git2txt only supported exporting the latest version of a repository. With this enhancement, users can now specify a commit hash, and the tool will generate a text representation of the repository at that exact state.