Repository navigation
Use GitPython for Git operations - #4
Closed
ThatXliner wants to merge 1 commit into
Closed
ThatXliner wants to merge 1 commit into
ThatXliner wants to merge 1 commit into
Conversation
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replace direct Git subprocess calls with GitPython for repository discovery, branch and merge checks, worktree management, ignored-file detection, and stale-reference pruning. Preserve the CLI behavior, including dirty-worktree protection and dry runs, and use NUL-delimited output to preserve filenames with spaces or Unicode.
Add GitPython and its lockfile entries, plus real-repository regression coverage for nested and linked worktrees, ignored files, detached worktrees, forced removal, and stale pruning.
Validation:
uv run pytest -q(89 passed),uv build, andgit diff --check.Closes #1.