jesseduffield / jesseduffield/lazygit
feat: Persistent Command Log
- Dominant language
- Go
- Stars
- 82.4k
- Forks
- 3k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 19
Description
Thanks for an amazing project! I actually wrote a blog post about `lazygit` recently (feedback welcome), just to share awareness in my circles: https://www.bwplotka.dev/2025/lazygit/
### Is your feature request related to a problem? Please describe.
Command log only shows actions lazygit did in the current session. It's very common to close lazy git and bring back after days on a certain repo, or accidently close lazygit and lose the history.
This is a problem when then trying to remember what was the branch on you touched in the recent past, what tag you were adding some time ago (was it you or some other person from outside), did you rebase to correct branch etc.
It would be epic if command log was persistent for a single user on a single machine.
### Describe the solution you'd like
A clear and concise description of what you want to happen.
Command log sharing a single file on filesystem (can be opt-in), like bash history.
### Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
* Not doing it.
* Having a server side shared history (too much work, not that needed, also one could do that on their own similar to bash history logs).
### Additional context
Add any other context or screenshots about the feature request here.
Contributor guide
Assessment
This issue has not been assessed yet.