Age | Commit message (Collapse) | Author | |
---|---|---|---|
2023-04-30 | Begin refactoring gui | Jesse Duffield | |
This begins a big refactor of moving more code out of the Gui struct into contexts, controllers, and helpers. We also move some code into structs in the gui package purely for the sake of better encapsulation | |||
2022-10-15 | fix: fix initial origin of commit message panel | Ryooooooga | |
2022-08-07 | allow rendering to main panels from anywhere | Jesse Duffield | |
2022-08-07 | move merge conflicts code into controller | Jesse Duffield | |
2022-08-06 | rename merging context to mergeConflicts | Jesse Duffield | |
2022-08-06 | refactor to only have one context per view | Jesse Duffield | |
2022-05-15 | refactor | Jesse Duffield | |
2022-05-08 | add option to always show unstaged/staged panels | HiromasaNojima | |
2022-03-19 | use generics to DRY up context code | Jesse Duffield | |
2022-03-17 | working again | Jesse Duffield | |
2022-03-17 | some more refactoring | Jesse Duffield | |
2022-03-17 | migrate files context to new structure | Jesse Duffield | |
2022-03-17 | move all refresh code into the one file | Jesse Duffield | |
2022-03-17 | move context keys into context package | Jesse Duffield | |
2022-03-17 | refactor contexts code | Jesse Duffield | |
2022-03-17 | fix some things | Jesse Duffield | |
2022-03-17 | start moving commit panel handlers into controller | Jesse Duffield | |
more and more move rebase commit refreshing into existing abstraction and more and more WIP and more handling clicks properly fix merge conflicts update cheatsheet lots more preparation to start moving things into controllers WIP better typing expand on remotes controller moving more code into controllers | |||
2022-03-17 | start refactoring gui | Jesse Duffield | |
2022-01-27 | better locking of merge panel state | Jesse Duffield | |
2022-01-26 | show only merge conflict files when there are merge conflicts | Jesse Duffield | |
2022-01-26 | improve merge conflict flow | Jesse Duffield | |
2022-01-22 | properly resolve cyclic dependency | Jesse Duffield | |
2022-01-15 | always specify upstream when pushing/pulling | Jesse Duffield | |
2022-01-15 | avoid deadlock in merge panel | Jesse Duffield | |
2022-01-15 | stop refreshing the screen so much | Jesse Duffield | |
2022-01-09 | shorten name | Jesse Duffield | |
2022-01-09 | refactor | Jesse Duffield | |
2022-01-09 | start removing direct calls to cmd.New from gui | Jesse Duffield | |
2022-01-09 | remove repo field | Jesse Duffield | |
2022-01-09 | start breaking up git struct | Jesse Duffield | |
2022-01-07 | rename variable to failedCommitMessage | Jakob Kogler | |
2022-01-07 | remember the message if commit fails | Jakob Kogler | |
In case a commit fails, e.g. because a pre-commit hook returns an error, lazygit will now remember the commit message and will suggest it during the next commit (e.g. after fixing the error of the pre-commit hook). | |||
2022-01-07 | refactor | Jesse Duffield | |
2022-01-07 | simplify how we log commands | Jesse Duffield | |
2022-01-04 | refactor sync test | Jesse Duffield | |
2022-01-04 | WIP | Jesse Duffield | |
2022-01-04 | WIP | Jesse Duffield | |
2022-01-04 | align Gui struct with GitCommand | Jesse Duffield | |
2022-01-04 | WIP | Jesse Duffield | |
2021-12-26 | Suggest existing remote for non-tracking branch | Marius Bergmann | |
Currently, when pushing or pulling a branch that has no tracking remote, lazygit suggests the (hard-coded) remote named 'origin'. However, a repository might not have a remote with this name, in which case the suggestion makes no sense. This happens to me quite regularly when I choose a more meaningful name than 'origin' for a remote. This change keeps the current behavior by suggesting 'origin' when there is either a remote with that name or no remote at all. However, when 'origin' does not exist, the name of the first remote is suggested. Suggest existing remote for non-tracking branch Currently, when pushing or pulling a branch that has no tracking remote, lazygit suggests the (hard-coded) remote named 'origin'. However, a repository might not have a remote with this name, in which case the suggestion makes no sense. This happens to me quite regularly when I choose a more meaningful name than 'origin' for a remote. This change keeps the current behavior by suggesting 'origin' when there is either a remote with that name or no remote at all. However, when 'origin' does not exist, the name of the first existing remote is suggested. | |||
2021-12-25 | implement signoff | Mark Sagi-Kazar | |
Signed-off-by: Mark Sagi-Kazar <mark.sagikazar@gmail.com> | |||
2021-12-06 | more efficient context diff size changing | Jesse Duffield | |
2021-11-01 | some refactoring in anticipation of the graph feature | Jesse Duffield | |
2021-10-25 | fix commit message prefix thingo | Jesse Duffield | |
2021-10-23 | add more suggestions | Jesse Duffield | |
2021-10-22 | simplify pull logic | Jesse Duffield | |
2021-10-20 | fix issue where upstream origin and branch were quoted together | Jesse Duffield | |
fix issue where upstream origin and branch were quoted together | |||
2021-10-17 | stop resetting scroll all the time | Jesse Duffield | |
2021-10-17 | fix editor | Jesse Duffield | |
2021-08-25 | Lint | Liberatys | |