Option to disable submodule synchronization
Please provide a way to disable GitKraken's logic for keeping track of submodule changes while performing various actions, like rebasing, checking out branches, cherrypicking commits, applying stashes, etc.
I'm using a repo at work that is big and slow, and trying to do any of these actions prevents GitKraken from actually doing the thing because it always gets hung up on the submodules.
There are some workarounds in the tool, like rebasing can be done instead by hard-resetting and cherrypicking everything. Other times, only the CLI can do it.
Comments: 11
-
10 Jul, '21
Craig ScottHaving similar issues. In my case, one of the git submodules has access permissions and I don't have access, so every attempt to update the submodule fails and also slows everything down.
-
31 Aug, '21
NoahYes same, I have a many submodules and takes a very long time to checkout a branch due to all of the submodules being updated every time (even if there is nothing to update...). Makes branch management very diffucult.
-
02 Sep, '21
Yves GraslandI have also work in repositories where I do not have permission to download some submodules. Gitkraken will always try to download them, fail (obviously), display useless error messages and even mess up the repository state : it puts submodules in a broken state where even the command line cannot disable them, and/or shows spurious "modifications" for them which it is not even able to discard, etc.
Everyttime I'm thinking "Kraken pleaaaaaase, stop messing with what you cannot handle properly!"
Having an option to disable submodule for some or all repositories would be great; it could also be an option to say "this submodule in this repository must not be updated automatically under no circumstances, I will update it manually if I need to". -
12 Dec, '21
Chris BeachI work with a repo with a large number of submodules. When I rebase my branch off of master often the submodules show up as uncommitted changes and rebase fails. The only solution is to discard the "changes" rebase then using the shell git submodule update --init. It is quite clunky
-
06 Feb, '22
Niccolò BettoI'm having the same issue, with my repository including big submodules (and them having their own recursive submodules), to the point where GitKraken is completely unusable. It takes ~5 minutes to load the repository, and then every action is slowed down to a crawl, usually taking ~30 seconds just to display changes when clicking on a commit.
There's also the fact that GitKraken is constantly using ~40% of my CPU when on said repo, and it only goes down to normal levels when switching to another repo.
Repo in question: https://github.com/skyline-emu/skyline -
11 Feb, '22
Hendrik WieseExperiencing these issues as well. Is this still open? Or is there already an option that I haven't found yet?
... considering the state of the suggestion, it's obvious that it's still open.
Voters please, this is a major road block for some of us! We need your voices :-) -
12 Mar, '22
BobThis would be nice. My Kraken merges always result in submodule conflicts which I have not found any documentation on how to resolve. Kraken provides no viable solutions for these conflict. I would like to checkout the source commit, disable submodule sync, checkout working commit and merge source commit into it. This should resolve the submodule conflicts which I will than handle as individual merges.
-
02 May, '22
JanPlease do this.
-
29 May, '22
TimothyPlease! The only reason why I haven't converted fully to GitKraken
-
16 Jul, '22
Josh+1 This makes it very annoying to work with large submodule dependent code bases.
I must run scripts, do hard resets, and sometimes delete folders when moving across major versions. Before I can make use of GitKraken's awesomeness.
Other tools do not have this issue ie CLI or SourceTree. -
26 Jul, '22
BobNever mind, I see this has been implemented.