NEW Lazygit release! (8 months worth of features)

okay guys well we're finally here it took way too long but I'm glad that uh the new release is about to come out um I'm just going to walk through some features that I find particularly cool but you'll need to look at the release notes to see the full story because there's quite a lot there so without further Ado let's jump into it okay let's jump into it so we'll start with just a couple of small UI changes the first one as you can see we've got this nice little SL scroll bars here compared to the chunky ones that we had previously so yes that design is patented um not actually um that looks quite nice um we've got some section headers in our uh key bindings menu now to make things a bit clearer we also have more uh tool tips um because many of these things warrant a bit of an explanation on what they do so that's cool um the section headers there was um was Stefan as was the slim scroll bar and you're going to find out the Stan behind many of the features in this in this release you can now see the little icons here a little little indicators on what button to press to jump to different side panels that was uh Maria Jose salano so thanks to Maria um there's now contextual key binding so if you see down here at the bottom uh it's got It's now showing actual key buying are the ones you probably want to be using in a given view so you don't have to jump to this menu menu to see what's what um and also if you for example are in a specific mode like say if I do a a rebase here it'll give me a suggestion on what button to press and in this case to press M so that you can go and abort the rebase that's cool um you you'll notice there's now for some errors like when a keying is disabled you'll see a little um uh error what is it this one you see a little error toe so for example here I'm trying to paste Comm without having copied anything I just get that little message there rather than uh a popup that I have to acknowledge because that popup can often be a little bit annoying um what else if you look at the files view you'll see that unstaged changes are now in white not red I we find that just a bit easier on the eyes um also we have colored icons now and that that's um thanks to aish sha um also if you let me just get rid of this and undo um you can now uh configure to have it when you maximize um a side view that it shows up at the top as opposed to on the side which could be useful for things like branches where you want to get a bit more information all with commits um it's not the default so you need to check the release Z to see how to configure that um we show fetching statuses in line uh likewise with um or in this case I actually couldn't fetch because I might have uh I can't recall what the issue is there but um likewise if you want to if you want to uh you know pull a branch um you'll see the status in line rather than in a popup menu and in this case I've got some configuration issue here so please ignore that um anyway back to my previous Branch uh um we always show the log graph by default now so you can see here like the actual individual commits um we show it by default in the minimized view previously you'd only see it if you in the maximized view um but users were asking for it so if you're if you're in a repo that has like loads of merge commits it might get a bit too noisy down there um but you can configure it to to not do that and you can check the releasees for that um what else mixed reset is Now the default when you press G on a branch so keep that in mind the reason for that is we found that mixed reset was just uh the one that almost everybody wants to use and it's kind of funny that it's called mixed and not soft because it's actually softer in a way than soft reset in that it doesn't stage files that get put in the working tree um and what else is there so that's just some small UI changes now I want to walk through some of the actual features so this is the fun part first of all previously when you were building a uh like a commit or you were trying to Stage individual lines you could um press V to select a range of lines um now you can do that in other places as well so down here in the commits view I can highlight multiple commits and then perform some action on them so for example say that I wanted to drop these three commits here um previously I'd have two options for that one is just going one by one and pressing D to drop them let me just undo back to where I was or you could go down to the next commit press e to edit it and then Mark these three as drop commits and then continue and both of those approaches are kind of laborious so what you can do now is you just uh either press V and then move down or you can just hold shift and use the arrow keys um you just highlight the commits you press D and you drop them so that's pretty cool and you can do that same thing with fix ups and squashes um even if you are doing an interactive rebase you can select multiple commits and move them around as well um so yeah it's awesome I've been using it for a while now um and uh it's just been hugely productive so by me that's been really cool um and you can use it for various things like if I um if I go to the the files panel again you can stage multiple files you can delete multiple at once um you can go to a um uh what was an example here you can go to an individual commit you can select multiple commit files if you want to add them to a patch and do something with them um so yeah that's pretty cool um okay uh something to note with that is because the V key binding was already used for past and commits we've had to resolve that conflict now so in order to copy commits is now shift C and to paste them it's shift v um if you just press regular C you get a little message here saying like how it's changed and how you can configure to go back to the old behavior um but uh yes that's just an unfortunate breaking change we had to make in order to support that vkey binding um uh in any uh list view um so that's cool and I'm just picking what will be a nice one to move on to after that so uh another one would be um you can now if you if I am let me just get a little commit here check this out blah blah if I type A commit message it now automatically WPS it for me and by wrapping I mean it's hard wrapping so it's adding a new line character I can go in here and I can have some more stuff and it rewraps it I can go and edit this guy and then add more stuff again um so that's really cool it's wrapping it 72 characters if that's too narrow for you you can change that in the config and again just check the release not to see how to do that um that was stepan how behind that one so thanks to Stan because that has been an awesome feature um what else okay here's a cool one so uh I don't know why it took us so long to do this but when I go to check out a remote Branch um like for example let's maybe this one here uh damn it that doesn't count because it already was I already had checked it out what a good example um this one here okay if there's a if you're trying to check out a remote Branch the haven't already checked out locally you now get an option to check it out as a local branch or as a detached head previously it would always do it as a detached head which pretty much no one ever wants um so now I can say yes do it as a local branch um and here I am so that's pretty cool um you can see that it's tracking the remote here uh so yeah that's just something that is a nice little quality of life Improvement because basically everybody wanted that from the beginning um um okay that was our Stephan how again so thanks to stepan for that um here's a cool one yeah I I go back to where I was because I really like that previous Branch uh here we are okay so I showed you before how that you you would start an interactive rebase by navigating down to the base commit and pressing e but that's kind of annoying you got to navigate all the way down press e then come back up to whatever you want to do now you just press I and Laser git will intelligently decide what the base commit should be so in this case uh it seems like it's picking the first merge commit but it would either pick that or it would pick uh whatever the the first commit on your branch is to be the base Branch so that uh should speed things up quite a bit um typically when you do a rebase you just want to do it for every every commit on your branch assuming that there's no merge commits there in a similar vein if you press shift s you now get uh the choice to just apply all fix up in your current brand so previously so I've got these four fix UPS here I'd come down to this commit press shift s and then say yes apply the fix ups but now I can just I don't need to navigate down I can just say yep just do all the ones in the current branch and it'll work um so that's cool and that's Stephan hel again um what else another one by stepan is viewing Divergence from the Upstream brand so maybe this is a good example here if you press U on a branch uh the F you get like the Upstream Branch options and the first option there is to view the Divergence so you can come in here and see you know uh what are the commits that are on the remote that I have to pull and what are the ones that I can push um so yeah that's an awesome feature um uh this one's complete Voodoo um what I'm going to do is I'm going to pop this and so often you'll be working on a PO request and someone gives you some feedback and says oh you should make this small change here and you want to have a clean commit history so you say okay well I'm going to make a fix up commit that targets the original commit that introduced this change so the problem you have is that you need to go through each of the commits and work out which one houses the changes that you have just made an amendment to so that is really laborious and what you can do now is if you press contrl s and on my system it's I've remapped it to shift F just because it was a clashing with a different key binding if you press contrs um it will laser git will go through the commits and find the matching commit um that's like the appropriate one to fix up so press shift F here boom it just moved down to this one here and you can see in the Reps helper this is the thing that it added maybe it was this thing no this thing um so you can come down here you press F to create a fixel commit or you can press a shift a to amend it um this is like the first cut so we want to get feedback on this it's very strict so when it matches something you know for certain it's the right commit but it also means if if there's any ambiguity it just doesn't attempt to find it and you're left to your own devices to find it um for example if your change only involves added lines like for example you've added a comment to an existing function then it won't actually know where the base is because it depends on on the removed lines to decide what the base is um yes that was Stefan again and that is just an awesome feature that I hope you can all try out and and give us some feedback on what else uh you can let me just delete this guy here you can now delete remote branches and tags if I press D on a uh Branch I can choose to delete the remote Branch likewise with tags and with the tag you going to specify the actual remote to uh uh to remove the tag from um so that was azreal SEC who made that feature so thanks to AAL you can also add a co-author to a commit so if I come down here and I say you know what uh actually I've already I've already done that on that commit let's say we go to this commit and I say I want to press a to amand an attribute I to say I am a co-author on this one because I helped out you can do that and then you'll see the little thing here and like uh you know cope uh GitHub is able to pause that and make sense of it so that's cool that was Oma who made that feature so thanks for that um you can now also filter commits by author so how do I filter commits let's just find out filter okay um I can filter by everything that Stephan how Hower has done I can do it based on all the stuff that I've done um so yeah that's a nice little feature that's why part 22 so thanks for that um you can now also change the branch sort order so if you press s in the branches view you can change the way it's sorted the default is by recency which is to say when was the branch last checked out and we use the ref log to find that out that's still the default but now you can do like alphabetical maybe that's what it's C me on um date based in terms of the last commit and then back to recency again so likewise with the remote branches view it's currently alphabetical I can also do date based um so yeah it's pretty cool um and that is hosaka who did that feature okay um next one is uh hard to demo but I'll just verbally describe it it's better bare repo support so that's John Whitley who did that previously if you use lasit to for example work on some dot files um it would just there was just various problems and we fixed all of them um so yes it works a lot better with bare repos now um cool so I think those are the main things I wanted to walk through but there's a lot there like if you just have a look at my notes here there's just so many things that have changed so I recommend you to have a read through see what's changed um like I said like there's like 600 commits here and yes it took way way too long to release this thing from now on we'll do um monthly releases um but uh yeah so um I'm super hyped to see how you find this new release and I'm looking forward to hearing all your feedback um so yeah I guess now I'm going to quickly just plug my new startup um but uh at any rate thanks for watching and I'll talk to you next time if you work at the typical tech company you know firsthand just how out of control subscriptions get you've got Confluence and jira and GitHub and slack and everyone's got their own subscription to it and the company just bleeds money to unused seats and bad pricing structures not to mention onboarding and offboarding of SAS apps is typically done by some person manually so if you leave a company and that person forgets to offboard you from something you'll still have access that means that the company's paying for your license uh unnecessarily and it poses a security threat because You' got an ex-employee who has access to their data me and a couple friends thought this was a big enough problem that we decided to quit our jobs and go fulltime on solving it and thus Zeno was born we're still early days but we believe we can save your company time and money and improve its security uh so check out our website zen. Au where you can join our free beta program um and let's see if we can save you some money so again that's zen. Au thanks for listening

Channel: Jesse Duffield

Views: 13,146

Keywords:

Id: _REmkoIyPW0

Length: 17min 0sec (1020 seconds)

Published: Sat Mar 23 2024