One recently learned about was adding gpg signatures from commits already pushed to remote: git rebase -i HEAD~5 change commits to 'edit' from 'pick' in the rebase doc then foreach commit do git commit --amend --no-edit -S then git rebase --continue Then when your done: git push --force-with-lease you will just add a signature to your past commits and others wont be changed!
Another good tip is when we have worked on a file but want to commit only parts of it, we can use the -p option to decide which lines should and shouldn't be staged.
Wow, amazing tutorial. After reading the git documentation I was really confused about some topics but this lesson made it clear to me. I really appreciate it thx for the great content.
This video is so goood! Important stuff af: I had seen the video when it came out.. But yesterday when I ran into a problem I realized I should see this video again properly
Really good video. On git restore -p enter "?" and git will show you the following: y - discard this hunk from worktree n - do not discard this hunk from worktree q - quit; do not discard this hunk or any of the remaining ones a - discard this hunk and all later hunks in the file d - do not discard this hunk or any of the later hunks in the file s - split the current hunk into smaller hunks e - manually edit the current hunk ? - print help
11:30 That's my biggest concern, git restore doesn't ask for confirmation. While I'm OK with that in other cases, when you are discarding changes, I feel like git should err on the side of caution.
Fantastic video. And very comprehensive. Only thing is that you never gave the CLI commands for the last exercise, "Splitting / Editing and Old Commit." I took good notes on everything else. Thanks for this post.
Here is the scenario, I created a branch from "develop" branch, then I created my PR against "develop". Code reviewer reviewed and Approved. Then I merged my branch (PR) with with "develop". I have have couple changes for example , commit A, B, C. so on. I just don't want changed " commit B". How to undo that form the merged PR and "develop" branch should nor have that "commit B"
Im bsc cs student and its project time...could you please mention some projects with tutorials bcs many project centers approach me with expensive fees...i can't afford it...help me guys
A like for a comprehensive overview of all the different possible things one can do in git to fix your mistakes. But a dislike for using a GUI tool almost half of the time. You should have used git status and git log to find information about the commit history. And you also used the GUI tool to checkout different branches, and even do cherry-pick! I'm not necessarily against using GUI tools, but the title of your video is "How to Undo Mistakes With Git Using the Command Line ". It implies that you will not use any GUI tools, only Using the Command Line! If instead you would have used Command Line ONLY and not used the GUI tool, it would have made explaining the actual git commands better. I think that using the GUI tool is less clear about what is actually going on. It is better to use the actual Command Line to explain how git works, especially since that's the title of your video!
I like the topic but I don’t like the use of gittower. The whole point and title of the video was using the command line. But over and over you switched to gittower. Everything should have been done on the command line. Otherwise it defeats the purpose as well as becomes an advertisement for gittower.
This is why I hate people, the entire video is free, it shows everything how to do as it claims using CLI, but you still had to comment to spread negativity somehow and pointed him showing his GUI tool to make the unrelated parts faster.
This video is good, but not great. What would make this video great is not shamelessly promoting that GUI app and sticking to demonstrating all scenarios with the commandline, just as the title of this video suggests. The presenter gets lazy by scenario #11 and doesn't demonstrate the commandline tasks, and only shows a summary of the commands at the end of the scenario. This is the problem with GUI apps, they make you lazy.
Probably the most important topic on GIT explained in the most simplest way. Awesome.
I have no idea why it took me three years to come across this video. It's a gem 🎉
One recently learned about was adding gpg signatures from commits already pushed to remote:
git rebase -i HEAD~5
change commits to 'edit' from 'pick' in the rebase doc
then foreach commit do
git commit --amend --no-edit -S
then
git rebase --continue
Then when your done:
git push --force-with-lease
you will just add a signature to your past commits and others wont be changed!
Not exaggerating, you are a gift from heaven, currently having problems with bad merges with master branch. This is helping me alot
I wished I could undo mistakes that I made in my life by using git :’)
F
Yes! you can, by following up DRY principle.
You can but you need admin privileges.
do it better next time, do not "commit" more mistakes :-)
did you commit?
That's a must-see for sure. Thanks for the content. Valuable af
Another good tip is when we have worked on a file but want to commit only parts of it, we can use the -p option to decide which lines should and shouldn't be staged.
Thanks for the tip!
Wow, amazing tutorial. After reading the git documentation I was really confused about some topics but this lesson made it clear to me. I really appreciate it thx for the great content.
Git is such an amazing tool!
thanks for the course and for making it freely available.
Great explanation!
Boom! Not panic anymore!
Great video. I like how you presented the use cases.
This video is so goood! Important stuff af:
I had seen the video when it came out..
But yesterday when I ran into a problem I realized I should see this video again properly
Oh Man I'm so happy to learn multiple things in this video
Really good video. On git restore -p enter "?" and git will show you the following:
y - discard this hunk from worktree
n - do not discard this hunk from worktree
q - quit; do not discard this hunk or any of the remaining ones
a - discard this hunk and all later hunks in the file
d - do not discard this hunk or any of the later hunks in the file
s - split the current hunk into smaller hunks
e - manually edit the current hunk
? - print help
Very well explained.. Thank you very much
Excellent job, Great for experts as well beginners....
Thank you for this drive, really it was an awesome tour to stack up the real base of "git".
Immediately added this video to my favourites. Thanks for the clear explanation!
Awesome video. Very gut explained and very helpfull tools. Thank you
awesome tutorial
Great information. Thanks for sharing.
I remember your voice from gitower tutorials :), thanks for the good job!
Nice. Been looking for this forever
Thank you for giving me a very detailed and very easy-to-understand explanation!!! RESPECT!!! 🙏
The one I was looking for a while, which resolves all the doubts so professionally :)
Very good tutorial! Learned quite a few things watching it. Thanks for making it!
Thank you bro!
Helpful sir thanks
The video is in my the top 10! Thanks! 👍🏼
Useful one.
If you are brand new to git, start with this video: ruclips.net/video/RGOj5yH7evk/видео.html
The most usefull lesson, big thx!
Thank you.
11:30 That's my biggest concern, git restore doesn't ask for confirmation. While I'm OK with that in other cases, when you are discarding changes, I feel like git should err on the side of caution.
Fantastic video. And very comprehensive. Only thing is that you never gave the CLI commands for the last exercise, "Splitting / Editing and Old Commit." I took good notes on everything else. Thanks for this post.
This was awesome. Thank you! Definitely will be checking out Tower now lol.
Thanks a lot, it was great!
You are awesome indeed. thanks alot!😍🙏 Thanks for providing such a crucial knowledge for free.
Exactly what I need!TY
Here is the scenario, I created a branch from "develop" branch, then I created my PR against "develop". Code reviewer reviewed and Approved. Then I merged my branch (PR) with with "develop". I have have couple changes for example , commit A, B, C. so on. I just don't want changed " commit B". How to undo that form the merged PR and "develop" branch should nor have that "commit B"
Genial. Muchas gracias.
Nobody covered these git commands before. Thanks a lot!
Can someone please tell me what are the commands for case # 17 at 54:01
Please provide link to your complete course.
please I want a full course talks about HTML, CSS, and JS all of them are standard version like not html5 or css3 or something. Thanks!
I've read it as how to do mistakes with Git and even with that I clicked never have blindly trust a channel like that!
Never been sooooo early!!
Yes
git restore . command do not work for deleting the untracked or unstaged files. Can we use git clean -fdx ?
How many 'CTRL Z' is allowed in Tower?
git restore is not finding as a command. What would be problem??
never been so late !!!!
Voila!
Make advance full course on c++ with project
hi freecodecamp is it possible can we get ppt?
This is a missing guide of my git journey.
Im bsc cs student and its project time...could you please mention some projects with tutorials bcs many project centers approach me with expensive fees...i can't afford it...help me guys
my parents:
Question:
1)when you squash two commit into one is it ok to delete the parents of that new commit
delete folder then clone again
Use RAR instead....
❤️
Just use SmartGIT :D
🎉
Wow
I also do videos about programming!😁
A like for a comprehensive overview of all the different possible things one can do in git to fix your mistakes.
But a dislike for using a GUI tool almost half of the time. You should have used git status and git log to find information about the commit history. And you also used the GUI tool to checkout different branches, and even do cherry-pick! I'm not necessarily against using GUI tools, but the title of your video is "How to Undo Mistakes With Git Using the Command Line
". It implies that you will not use any GUI tools, only Using the Command Line! If instead you would have used Command Line ONLY and not used the GUI tool, it would have made explaining the actual git commands better. I think that using the GUI tool is less clear about what is actually going on. It is better to use the actual Command Line to explain how git works, especially since that's the title of your video!
I like the topic but I don’t like the use of gittower. The whole point and title of the video was using the command line. But over and over you switched to gittower. Everything should have been done on the command line. Otherwise it defeats the purpose as well as becomes an advertisement for gittower.
Second
$ git restore .
"Using the command line" is an unnecessary addition to the title, given that a quite relevant portion of the video shows off his GUI tool.
This is why I hate people, the entire video is free, it shows everything how to do as it claims using CLI, but you still had to comment to spread negativity somehow and pointed him showing his GUI tool to make the unrelated parts faster.
This video is good, but not great. What would make this video great is not shamelessly promoting that GUI app and sticking to demonstrating all scenarios with the commandline, just as the title of this video suggests. The presenter gets lazy by scenario #11 and doesn't demonstrate the commandline tasks, and only shows a summary of the commands at the end of the scenario. This is the problem with GUI apps, they make you lazy.
Git Tower looks nice, but it's not available for GNU/Linux, so I'll stick with command line.
Use GitKraken
soooo useful, thank you!!!