Stefan Haller 910a61dc46 Make "merged" take precedence over "unpushed" ... Previously, when rebasing a branch onto a newer master, all commits from the previous fork point up to its head were marked red (unpushed), including the commits that are on master already. While this is technically correct from the perspective of the current branch's upstream, it's not what most people expect, intuitively; they want to see where the current branch starts, relative to master. So all commits of master should be green, and then the commits of the current branch in red.		2023-05-12 22:56:58 +02:00
..
git_commands	Make "merged" take precedence over "unpushed"	2023-05-12 22:56:58 +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	rename patch manager to patch builder	2023-03-19 16:35:57 +11: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_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
git.go	rename patch manager to patch builder	2023-03-19 16:35:57 +11:00