Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
action-homebrew-bump-formula
Created with
brew bump-formula-pr
.release notes
That takes too long! Now you can just press 'r' followed by 'b' to rebase onto the base branch (which defaults to origin/main).
See the divergence count from the base branch
(Divergence from base branch display by @stefanhaller in jesseduffield/lazygit#3613)
You can now also configure to see the divergence from a branch and its base branch with the following config:
This shows the divergence count in blue, next to the yellow count of divergence from the upstream branch. This is admittedly noisy, so it's an opt-in feature. But I think the noise is worth it.
If you set the config value to 'onlyArrow' it's a lot less noisy:
See detailed divergence from base branch
(Add command to show divergence from base branch as a left-right log by @stefanhaller in jesseduffield/lazygit#3614)
By pressing 'u' then 'b' on a branch you can see the divergence view for that branch compared to its base branch
Improved 'Find commit for fixup' feature
(Improve the "Find base commit for fixup" command by @stefanhaller in jesseduffield/lazygit#3602)
'Find commit for fixup' is not a very catchy name for this feature but I can't think of anything better at the moment. Nevertheless! The idea is that you often want to know for a given set of changes, which commit ought they be included in? Just press
ctrl+f
when in the files panel and lazygit will jump the cursor to the appropriate commit to fixup.With this release, the feature is smarter and more lenient so it's more likely to find you a match. If you haven't tried this out you should really give it a go!
find-commit-demo.mov
Other Enhancements 🔥
shift+m
you get the option to do a regular merge or a squash merge. If you already have muscle memory for regular merge; don't worry: it's the same sequence of keypresses.similarity-demo.mov
gui.expandedSidePanelWeight
by @stefanhaller in Add user configgui.expandedSidePanelWeight
jesseduffield/lazygit#3623lg-multi-author-select.mov
Fixes 🔧
Maintenance ⚙️
copyloopvar
to enabled linters by @kyu08 in Addcopyloopvar
to enabled linters jesseduffield/lazygit#3586lint
to make target by @kyu08 in Addlint
to make target jesseduffield/lazygit#3593goconst
in the future from.golangci.yml
by @kyu08 in Delete the TODO comment about enablinggoconst
in the future from.golangci.yml
jesseduffield/lazygit#3596rebase_onto
demo test to match new the rebase menu title by @AzraelSec in Updaterebase_onto
demo test to match new the rebase menu title jesseduffield/lazygit#3636actions/checkout
,actions/setup-go
,actions/cache/restore
,actions/cache/save
by @kyu08 in Bumpactions/checkout
,actions/setup-go
,actions/cache/restore
,actions/cache/save
jesseduffield/lazygit#3594Docs 📖
New Contributors
Full Changelog: jesseduffield/lazygit@v0.42.0...v0.43.0