LazyGit makes you 10x faster while using Git.
HTML-код
- Опубликовано: 20 авг 2024
- Are you tired of complex Git commands and endless switches between branches? Enter LazyGit! In this video, we'll explore how LazyGit can revolutionize your Git workflow, especially if you're a beginner. From its intuitive interface to its powerful functionalities, learn how this tool streamlines your version control process. Discover how to manage branches, resolve merge conflicts, and visualize your repository's status, all within a user-friendly terminal UI. Join us as we dive into LazyGit, making Git easier and more accessible for everyone. Whether you're a seasoned developer or just starting, this guide will help you harness the efficiency of LazyGit and take your Git skills to the next level!
#git #github #linux #terminal #linuxtips #versioncontrol #vcs
lazygit is just awesome. At 4:30 you pull in changes onto the master branch. There is a simpley way:
- fetch the latest commits (usually this is already done by lazygit in the background, otherwise press f in the files section).
- select the master branch and press f for "fast forward". This will fast forward your main branch to the state of the remote.
- Merge as always...
This saves me a ton of time every single day...
This video about LazyGit is both interesting and informative
Fake comment
Ok this-person-does-not-exist
4:13 How would I do this for git over ssh?
I see you switched to the third panel by pressing 3 on the keyboard, but how did you switch to Remotes?
Press [ and ] for left and right respectively. @aliventurous
good demo
4:40 And what do I do when I need to do "git pull --rebase"?
I am not sure if it supports this command natively. But you can create your own command.
github.com/jesseduffield/lazygit/blob/master/docs/Custom_Command_Keybindings.md
There are rebase options baked in, pres '?' to get a full list of commands per pane.
hi I am having some issues, it asks for user name & password and everytime it fails
Try to make it work with normal git commands first. I don't think this is issue with LazyGit
Use PreShared Keys and you will no longer have to deal with such ancient type of credentials.
@@sagaratytube thanks, fixed it, it had some issues which https but it works fine with ssh clones
3:54 "Hitting git will create the commit."
Even while editing the Commit description?
c will show dialog. And after adding message hitting enter will create a commit.
2:27 how to switch from local branches to remote branches
@mitesh5189 press right square bracket
@@sagaratytube thanks man
You didn't explain how the remote url was set
It was set automatically when I cloned repo. You don't have to explicitly set for LazyGit. It will read from the .git directory
@aliventurous
Ah I see. But what if you initialized the repo locally first? Is there a way to set the remote url via lazygit?
Not sure about that. Need to check documentation.
This is AI-generated.
Again, I don't think that's the case, if you go to the first videos in the channel it's an actual person talking, but he/they changed to an AI voice, maybe because it's easier to understand (at least for me)
yet still helpful
I like this voice. I'm looking for this AI voice but can't find it 😢
You're AI generated
The voice is, but I don't think the script is. If you check his older videos, you will hear his voice and he has a very thick accent. He must've switched to an AI voice because of it.
Um... Cool but... I mean... Ever seen what zsh git aliases can do for you?
I will check. Thanks.
It's fine to like something different.
From what I have seen, shell aliases typically have a much narrower feature set.
@@sp3ctum that's doubtful. Shell aliases allow you to add more options to the command after you type the alias in. Nothing is off the table.
Whereas with GUI/TUI tools you almost never have access to more advanced features. Half of the UI tools I used fail when I either try to add an empty commit, or pass options to the server when pushing.
Learning an UI tool is not worth the effort if you are a proficient terminal user.
@@__mrmino__ ah I see what you mean. You're right about the commands not being customizable enough. Sometimes I have had issues when pre commit hooks are misconfigured and don't work reliably. This would be very easy to fix or bypass in the shell, but lazygit doesn't have good support for this if I also want to save my commit message and try again.
But some features of lazygit are very nice out of the box. For example, it's very easy and intuitive to split patches from old commits and add them to others, or to create new ones from them.
I guess one has to make a choice between developing their own aliases and workflow, or to adapt to someone else's.
@@sp3ctum the better patch mode is a serious plus, it's the only feature that I'm missing when working with git in the shell. Editing patches in vim is ok, but this could be so much better.