Add support for git-svn type working copy#5611
Open
bigfroggit wants to merge 2 commits into
Open
Conversation
added 2 commits
February 21, 2026 23:07
1. Can detect repository automatically. 2. Remap push/pull/fetch commands to git svn dcommit/rebase/fetch commands. 3. Command log window will show the repository type.
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.
PR Description
I am not a software programmer, but only a ASIC designer, so I don't known GO language. But in my development environment, only SVN can be use now. I ready like git, and lazygit, so I want to use git-svn tool to handle my SVN working copy, so I can use lazygit. But for git-svn type working copy, pull/push operations are not same to git type working copy, and only should use git-svn rebase for pull operation. So I add some code to let lazygit to support git-svn type working copy. The modifications are generated by AI, but I also tried to make the code be logic right base on my comprehension on lazygit code. The main chages are:
If you like my modification, I would be very happy if you can merge to main branch.
Please check if the PR fulfills these requirements
go generate ./...)