Stefan Haller 3cddd7cfa5 Don't keep commits that become empty during a rebase ... The only exception is when moving a custom patch for an entire commit to an earlier commit; in this case the source commit becomes empty, but we want to keep it, mainly for consistency with moving the patch to a later commit, which behaves the same. In all other cases where we rebase, it's confusing when empty commits are kept; the most common example is rebasing a branch onto master, where master already contains some of the commits of our branch. In this case we simply want to drop these.		2023-05-20 21:10:03 +02:00
..
git_commands	Don't keep commits that become empty during a rebase	2023-05-20 21:10:03 +02:00
git_config	remove deprecated calls	2022-09-17 15:10:41 -07:00
hosting_service	feat: add gitea to hosting service	2023-04-18 16:16:09 +00:00
models	Store commit.Action as an enum instead of a string	2023-04-15 08:36:03 +02:00
oscommands	Change OpenCommand to Open and OpenLinkCommand to OpenLink	2023-04-13 13:14:00 +02:00
patch	Refactor interface for ApplyPatch	2023-05-20 20:54:39 +10:00
testdata	Support opening lazygit in a submodule	2019-05-12 17:59:49 +10:00
types/enums	more refactoring	2022-01-04 09:07:15 +11:00
git.go	Refactor interface for ApplyPatch	2023-05-20 20:54:39 +10:00
git_cmd_obj_builder.go	WIP	2022-01-04 09:07:15 +11:00
git_cmd_obj_runner.go	fix(loaders/file.go): changed to ignore stderr when loading git status	2022-09-19 18:46:32 +09:00
git_test.go	feat: add GitVersion struct	2022-12-30 20:01:14 +09:00