summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2023-08-07Updated README.mdv0.40.2README-bot
2023-08-08Fix seg-fault when opening submodule in nested folder (#2903)Jesse Duffield
2023-08-07Fix seg-fault when opening submodule in nested folderJesse Duffield
2023-08-07Fix opening lazygit in a bare repo with specified worktree (#2902)v0.40.1Jesse Duffield
2023-08-07Support bare worktrees where worktree does not have its own .git fileJesse Duffield
This was on oversight on my part: I assumed that the --work-tree arg was always intended for use with linked worktrees which have a .git file pointing back to the repo. I'm honestly confused now: seems like there are three kinds of worktrees: * the main worktree of a non-bare repo * a linked worktree (with its own gitdir in the repo's worktrees/ dir) * a random folder which you specify as a worktree with the --work-tree arg I'm pretty sure the --work-tree arg is only intended to be used with this third kind or workree
2023-08-07Test bare repos with dotfile setupJesse Duffield
2023-08-07Use nerdfont version 3 in demos (#2901)Jesse Duffield
2023-08-07Use nerdfont version 3Jesse Duffield
Turns out I was on version 2 when recording these. I've switched to v3 now.
2023-08-07Don't run the check-required-label check on master (#2896)Stefan Haller
2023-08-07Don't run the check-required-label check on masterStefan Haller
master doesn't have a label, so CI for master currently always fails.
2023-08-07update worktree icons for NerdFont V3 (#2895)keybinding-menu-headingsStefan Haller
2023-08-07Updated README.mdREADME-bot
2023-08-07Import stefanhaller's tcell fork for real rather than just replacing it (#2888)Stefan Haller
2023-08-07👽️ update worktree icons for NerdFont V3Saafo
2023-08-06Bump gocuiStefan Haller
... and import stefanhaller's tcell fork for real rather than just replacing it This solves the problem that people trying to "go install github.com/jesseduffield/lazygit@latest" would get the error go: github.com/jesseduffield/lazygit@latest (in github.com/jesseduffield/lazygit@v0.40.0): The go.mod file for the module providing named packages contains one or more replace directives. It must not contain directives that would cause it to be interpreted differently than if it were the main module.
2023-08-06Updated README.mdREADME-bot
2023-08-06Fix README.md typo backkground -> background (#2884)Stefan Haller
2023-08-05Fix README.md typo backkground -> backgroundMattias Johnson
2023-08-05Updated README.mdv0.40.0README-bot
2023-08-05Fix confirmation view sizing (#2879)Jesse Duffield
2023-08-05Fix confirmation view sizingJesse Duffield
The proper fix is to actually have these two functions share code, or for views to be able to manage their own heights based on their contents. But I want to get this out for the sake of a Lazygit Anniversary release.
2023-08-04Add more demos (#2874)Jesse Duffield
2023-08-04Add custom patch demoJesse Duffield
2023-08-04Add worktree demoJesse Duffield
2023-08-04Add custom command demoJesse Duffield
2023-08-03Add undo/redo demoJesse Duffield
2023-08-03Add filter demo to READMEJesse Duffield
2023-08-03Move features to top of readme (#2867)Jesse Duffield
2023-08-03Move features to top of readmeJesse Duffield
2023-08-03Add more demos to the README (#2866)Jesse Duffield
2023-08-03Point to new demosJesse Duffield
2023-08-02Add demo for staging linesJesse Duffield
2023-08-02Add demo for amending old commitJesse Duffield
2023-08-02Add demo for filtering branchesJesse Duffield
2023-08-02Support mp4 videos for demosJesse Duffield
For all videos but the first video in the readme we want to use mp4 because it's faster, better quality, smaller, and allows you to play/pause (don't quote me on the smaller part). HOWEVER: github won't let us reference mp4s stored in our repo from the readme, like it does for gifs (who knows why). This is annoying because it prevents us from easily re-recording things if the UI changes. So I've got the logic for recording to mp4 but I'm thinking of sticking to gifs for now
2023-08-02Remove file watcher code (#2865)Jesse Duffield
2023-08-02Remove file watcher codeJesse Duffield
Now that we refresh upon focus, we can scrap this file watching code. Stefan says few git UIs use file watching, and I understand why: the reason this code was problematic in the first place is that watching files is expensive and if you have too many open file handles that can cause problems. Importantly: this code that's being removed was _already_ dead.
2023-08-02Auto-refresh on window activation (#2854)Jesse Duffield
2023-08-02Refresh when the terminal window gets the focusStefan Haller
2023-08-02Bump gocuiStefan Haller
2023-08-02Point tcell at stefanhaller's forkStefan Haller
This is temporary as long as https://github.com/gdamore/tcell/pull/599 is not merged. Once that PR is merged, we can revert this.
2023-08-02Stop worktrees view from stealing the window (#2863)Jesse Duffield
2023-08-02Appease linterJesse Duffield
2023-08-02Increase timeout for linterJesse Duffield
we've had a timeout issue in CI
2023-08-02Fix focus issueJesse Duffield
When opening lazygit with `lazygit log` the worktrees view was appearing in front of the files view. This is because it had higher precedence than the files view in the ordered view mapping, and that was because it originally was in the branches window so it was further down the list. The reason this didn't cause issues on typical startup is that the files context is activated at the start so it is brought to the front.
2023-08-02Update README.mdJesse Duffield
2023-08-01Update README.mdJesse Duffield
2023-08-01Show visual explosion effect when nuking worktree (#2861)Jesse Duffield
2023-08-01Wait in demo after setting captionJesse Duffield
This looks nicer than waiting a second and then showing the caption as the action begins
2023-08-01Add explosion animation when nuking working treeJesse Duffield
I've been thinking about this for a while: I think it looks really cool if nuking your working tree actually results in a nuke animation. So I've added an opt-out config for it