Listing all the commands on the side like that, makes this video a great memory aide. I frequently come back just to reread the list. A+ for thoughtfulness.
This is probably one of THE best tutorials I've seen on GIT. Assumes no prior knowledge and walks you through step by step. keep up the good work Tim :)
After watching multiple tutorials that all seemed to target just the distributed environment, I was getting very frustrated. Your tutorial is by far the best I've viewed. It gave me a great start using git in a non-distributed way, which is what I needed to do. Thank you so much for creating this tutorial and making what seems to be a complex subject much more easily grasped.
Thanks a lot, great explanation! by the way "git add ." does add deleted files, must be from newer version For any other total beginners to bash like me, if you noticed how when he did the "git commit" notepad opened up, but for you the file got opened in the command line, you can set it up to open notepad like this: git config core.editor notepad or adding the pathfile to your prefered program, for example: git config --global core.editor "'C:/Program Files/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin" (the last parameters are running options for notepad)
I'm 17 minutes in and it's already an excellent tutorial and perfectly presented set of contents. Super visual explanation of everything step by step. Tim you are a beast ! Thanks ! I'm your new biggest fan lately !
You are an excellent author and always do a great job presenting the material your in video tutorials. Always very clear, practical and concise. Nicely done!
I'm a mech engineer by trade and i'm trying to learn more flexible coding languages rather than using things like Matlab. Your videos are amazingly clear and always answer the questions I'm thinking as I watch your videos. Super well done and thank you.
The absolute best video tutorial on git for beginners! Tim, thank you for your wonderful work. When watching your videos you can literally feel how much you care about teaching, you are explaining so thoroughly and making sure it's detailed and structured.
I wil be attending a coding bootcamp in a few weeks and for preparation i wanted to learn git. I watched a few tutorials and introductions and got an idea how git works. But your tutorial was different and made me REALLY understand what I can do with it. So easy to grasp yet learning a lot new stuff. This was awesome. Thank you so much!
Thanks Tim Corey - i had for years been avoiding moving from SVN to GIT and your tutorial was absolutely fantastic and simple to understand in how you built up the concepts. Now I love GIT - all thanks to you. Please keep it up - your style of instruction is really good.
Okay. I allways dimissed git since I have not had the time but last night I watched your calm but clear and foward video and today after about 45min. I have moved to git at work with our main onlineshops. I use Atom btw. wich works great. The only thing I was missing is that git may ask you "Tell me about yourself" to set a username and mail and there was a bug. If anyone encounters it as I did, just google it. The sequence is key. Anyways, thank you a lot, Timothy, you answered a lot of questions others forget to mention.
Working with it right now and yes, I do find it beneficial. I saw you make tutorials for C# aswell. I'll recommed your chanal to a friend. If you make every tutorial like this, he will soon be the new champ in his new company.
Great video. I didn't understand everything the first time that I watched it, but after getting more hands-on practice using git in Visual Studio, I watched it a second time. This time it clicked, and I got a better understanding regarding some of the details, and what is going on under the hood.
I'm a bit late to the party, but having now watched this video, I think I now feel pretty comfortable with using Git! That made a lot of sense! Thanks.
For the "git commit" command in 17:50: If the notepad file does not open up and the same message appears in the console. press "esc" then type ":wq". It is the same as saving and exiting the notepad file
I think it is very good time to update this lesson to newest versions of Git and Visual Studio :) I would love to see it updated. And I think, that not only me.
Nice tutorial, very easy to understand. One suggestion would be to have some sort of visual representation of what is going on on the branches, their graph. Also, more info on resolving conflicts, and seeing the commit history inside git.
GIT is so powerful it's scary, but this video goes a long way toward ameliorating the fear. What are the best practices for preparing for a GIT failure of some kind? Do you have plans to do a more advanced video that will explain more about exactly how GIT performs this magic? (Or do you know of some existing ones?)
Hi Tim, Thanks a lot for the tutorials. These are really helpful. Could you please create a detailed tutorial on working with Team Foundation Server (TFS) Source Control System specifically folder mapping, check out , checkin and merge process. Please share the link if there is already one. Thanks.
I watched plenty git tutorials in the last week or so, and this is probably the best so far. Very simple explenations, very easy to understand, thank you very much! Can you make a MVC 5 web app from start to finish video like you did the one on Win Form (Creating a C# Application: From idea to finished product) ? I think that would be the best MVC 5 tutorial on youtube (and believe me, I think I watched them all :)) Once again, you are a great theacher, and I ask God One and Only to give all the best for you and your family. All the best form Sarajevo, Bosnia and Herzegovina
+Timothy Corey This is great tutorial. I wish if you could make more C# example tutorials like the one Creating a C# Application: From idea to finished product. For example, how to make classes with other example, and maybe you could use grid control to display data. Note: Windows Forms are much better and easier to work with. Thanks
+Timothy Corey Git Hub has BIG problem. It is not free. If you use Public repository and dont want to pay, than all can see your project. Why would someone work and give it for free?
Tim -- Do you recommend using the source control features built into Visual Studio? As opposed to command line with Git Bash and /or UI such as GitHub Desktop?
I recommend learning the command line but then using the visual tools provided (in Visual Studio, standalone, etc.) There will be times you need to use the command line, plus knowing how the command line operates will help you better understand the GUI tools.
Hi Tim, Recently I have had to use SourceTree. Every time I realize I have to undo stuff after a commit (or after a few commits) and just go back to the state of the project at a certain revision, I assume that I can "simply roll back" because I use git (via SourceTree) but when I double click on any commit to check it out and take it from there, I always get a warning message that this action would create a detached head, etc... I have seen a lot of posts that deal with hard resetting, etc... but I wonder how would one just roll back without causing problems such as detached head then, and not having to reset all the previous commits? Thanks
I think the best option here would be to a "git checkout -b " That will create a new branch that only has up through the specified commit. I typically use the command line so I'm not sure how SourceTree does it but that command should help you out.
Great tutorial, thanks a lot Tim, really helped me. Could you comment on what Forks are and just mention the commands related with them? or Do you have a tutorial on them? Thanks a lot once again !
I don't have a tutorial on it, but forks are actually not too complicated. Essentially it is just a copy of a repository. So what you do is this: if you can see a repository but do not have access to make direct modifications (most of Github works this way), you make a fork (a copy of the repo onto your profile that you then have access to). From there, you can make changes to your copy. When you are finished making changes, you go to the original repository's site (the one you had read-only access to) and you make a pull request. Basically, a pull request is just a link to your repository and any notes you want to attach (like "I fixed bug 123 for you"). The owner of the original repository can then review your changes and merge them into their repository, they can ask you to make further changes, or they can reject your changes. That's all it is. Does that make sense?
Absolutely makes sense Tim, now I understand. Thank you very much for your prompt answer and your time, it is great ! I am sure that with your unique way of explaining things, you saved me some time here. Best regards.
After watching several tutorials,this is one of the best tutorials.Thanks for your clear explanation. but I have one doubt, if I have a software with multiple software versions, what should I do if I am going to use Git for versioning control, Should I put every earlier version as branches and the put current release as master?
The most common thing to do in this situation is to tag your releases (git-scm.com/book/en/v2/Git-Basics-Tagging). Essentially, whenever you are saying "this commit represents the last code to go out the door for this particular release" you add a tag. You don't need a new branch. So you have one branch but lots of tags that identify where the code was at each release point. If you needed to patch an older release without moving them to a newer release, you could check out that commit into a new branch and apply the patch. You could then merge that change into master or you could leave it alone.
Definitely git. Hands down. It is easier to work with, it is easy to maintain, and easy to move from one host to another. Plus, most of the industry uses it.
Yes it is an there usually isn't a con to it. Once you have merged your changes into master, you can safely delete the branch because you haven't lost anything. Everything is in master. The only dangerous thing is if you delete a branch that has not been merged into master (or another branch). Then those changes will be gone and there isn't a good way to get them back (there is a possibility of getting a deleted branch back but you shouldn't plan for it).
Around 17:30 where you explain git commit I get an error. Gvim is my text editor, and it opens up after typing "git commit", but I also see "Aborting commit due to empty commit message." and a new line "(gvim:21814): GLib-GObject-WARNING **: cannot retrieve class for invalid (unclassed) type ''"
thx for your work but need here little help im starting new c# and i dont know what video of yours should i start can you just point me at the right path to begin
Back then GitHub didn't offer free private repos like BitBucket did, which is why I demonstrated it on BitBucket. Now I would probably use Azure DevOps.
Excellent explanation. When I do git push -u origin master nothing happens and the cmd seems to "freeze". What can be happening? (I have to do Ctrl + C to cancel)
When committing for the first time 16:36 if you get the following error: fatal unable to auto-detect email address . You can solve this by setting your email address by typing: git config --global user.email "you@example.com" Then try committing again and it should work.
Ok I get it, Git is designed to be obfuscated and to seem needlessly more complicated than it needs to be. The question is, what is a good alternative to not having to deal with Git?
It isn't designed to be obfuscated or to seem complicated. Actually, once you understand what it is doing, most of the commands are incredibly intuitive. However, what it is doing is incredibly complex so sometimes there are complex things you need to do to make it do what you want. As for the alternatives, Git is the industry standard. You need to know it if you want to be viable in the market. There are definitely places that don't use it, but they are quickly becoming the minority. Besides, Git is the best solution for source control we have and source control is imperative.
I am not sure what you are looking to do. The phrase "after Git starts" is interesting. Git doesn't really run. It just sits there until you call it. So for example, if I open up git bash at the root of my project, that is essentially just a command prompt. In fact, my command prompt acts just like the git bash. It is only when I issue a command like "git status" that git is called and it does something. You could do a batch statement so that when you called a certain command, multiple git commands are issued at once but I don't see that as helpful. For instance, if you want to be sure that your local copy of the repository is up to date with the remove version, you would want to run a few commands but you need to make decisions based upon the results. For instance, I would first start with "git status" to identify the state of my local repo. If I have uncommitted files, I would then run a commit command or a stash command, depending on what I wanted to accomplish. If there were no uncommitted files (or after I had handled them), I would run a "git pull". That would bring in the commits from the remote repo and it would merge the changes with my local commits. If there were differences that caused a merge conflict, I would need to deal with those issues next and create a merge commit. As you may notice, none of these steps should be done blindly. That is why the git tools out there don't do these tasks automatically and why you cannot find out how to do this yourself. If I misunderstood your question or if you have further questions, please let me know.
I've looked and looked, and can't get passed this error when trying to push for the first time with . I replace "origin" with my repository name . Here is the error I keep getting when trying to push: Updates were rejected because the tip of your current branch is behind its remote counterpart. Integrate the remote changes. Any ideas?
It seems as though your remote branch has been updated since your local branch was updated. Do a "git pull" first and merge the changes locally, then do your "git push".
If any can help! How can i "Push" new branches to the remote "origin"? In git-demo if i create new branch "Dev" how can i push dev branch to to remote repo?
If you have set your origin as your default upstream (this happens by default if you clone from a repo) then you would just do a "git push". If you have not set it as your default upstream, you would do a "git push origin dev" to push to the dev branch of origin (even if it doesn't exist yet).
This is not just a tutorial, it's a Masterpiece of how things should be explained ... I'm really speechless and impressed
От радости ш тттт
Old tutorial. Still relevant and excellent. Excellent straight forward, hands-on, practical walkthrough and explanations for beginners. Thanks Tim.
You are welcome.
Listing all the commands on the side like that, makes this video a great memory aide.
I frequently come back just to reread the list.
A+ for thoughtfulness.
Thanks for the feedback. I might start doing that more.
This is probably one of THE best tutorials I've seen on GIT. Assumes no prior knowledge and walks you through step by step. keep up the good work Tim :)
I appreciate the kind words. I'm glad you found it valuable.
0:00 - DIY without GIT
4:15 - GIT goals
5:53 - Getting started
18:39 - Changing the files
21:19 - Adding new files
25:25 - GIT branch
28:47 - Deleting files in branch
32:56 - deleting GIT branch
34:59 - Making changes in GIT branch and merging changes
45:21 - Merging changes between multiple branches
57:51 - Remote GIT (Bitbucket)
1:07:45 - View commits
1:13:31 - pushing commits to remote
repository
1:18:59 - joining a project form remote GIT
1:28:10 - summary
Thanks! I added it to the description.
@Tim, you kept it very simple...no beating around the bush, straight to the point. Loved your tutorial!!!
Thanks!
After watching multiple tutorials that all seemed to target just the distributed environment, I was getting very frustrated. Your tutorial is by far the best I've viewed. It gave me a great start using git in a non-distributed way, which is what I needed to do. Thank you so much for creating this tutorial and making what seems to be a complex subject much more easily grasped.
I'm glad this tutorial made learning git a bit easier for you. Thanks for letting me know.
Thanks a lot, great explanation!
by the way "git add ." does add deleted files, must be from newer version
For any other total beginners to bash like me, if you noticed how when he did the "git commit" notepad opened up, but for you the file got opened in the command line, you can set it up to open notepad like this:
git config core.editor notepad
or adding the pathfile to your prefered program, for example:
git config --global core.editor "'C:/Program Files/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin" (the last parameters are running options for notepad)
I'm 17 minutes in and it's already an excellent tutorial and perfectly presented set of contents. Super visual explanation of everything step by step. Tim you are a beast ! Thanks ! I'm your new biggest fan lately !
Glad it was helpful!
Watched on 1.25x and I can honestly say this is the best Git tutorial out there, subbed!
Awesome! I'm glad you found it so useful.
You are an excellent author and always do a great job presenting the material your in video tutorials. Always very clear, practical and concise. Nicely done!
Thank you!
I deeply appreciate your timeless insights and willingness to share them. Looking forward to checking out your videos! Thank you.
You are welcome!
I'll second the appreciative comments below that give this tutorial a big wrap Timothy...very clear, concise, informative and useful, many thanks!
I'm a mech engineer by trade and i'm trying to learn more flexible coding languages rather than using things like Matlab. Your videos are amazingly clear and always answer the questions I'm thinking as I watch your videos. Super well done and thank you.
That’s great to hear!
Seeing that after seeing your new videos, shows the long path of making this channel more evident. Great Video. Again Thanks for the content
You are welcome.
Thank you so much Tim. I have watched tonnes of videos before, but there is no match to yours. Keep uploading new videos...... Many cheers to you.
Glad you like them!
The absolute best video tutorial on git for beginners! Tim, thank you for your wonderful work. When watching your videos you can literally feel how much you care about teaching, you are explaining so thoroughly and making sure it's detailed and structured.
You are welcome.
I wil be attending a coding bootcamp in a few weeks and for preparation i wanted to learn git. I watched a few tutorials and introductions and got an idea how git works. But your tutorial was different and made me REALLY understand what I can do with it. So easy to grasp yet learning a lot new stuff.
This was awesome. Thank you so much!
Thanks Tim Corey - i had for years been avoiding moving from SVN to GIT and your tutorial was absolutely fantastic and simple to understand in how you built up the concepts. Now I love GIT - all thanks to you. Please keep it up - your style of instruction is really good.
That's great! I'm glad I was able to help you understand git. It is an amazing tool, it is just hard to initially understand.
Okay. I allways dimissed git since I have not had the time but last night I watched your calm but clear and foward video and today after about 45min. I have moved to git at work with our main onlineshops. I use Atom btw. wich works great. The only thing I was missing is that git may ask you "Tell me about yourself" to set a username and mail and there was a bug. If anyone encounters it as I did, just google it. The sequence is key. Anyways, thank you a lot, Timothy, you answered a lot of questions others forget to mention.
Working with it right now and yes, I do find it beneficial. I saw you make tutorials for C# aswell. I'll recommed your chanal to a friend. If you make every tutorial like this, he will soon be the new champ in his new company.
Great video. I didn't understand everything the first time that I watched it, but after getting more hands-on practice using git in Visual Studio, I watched it a second time. This time it clicked, and I got a better understanding regarding some of the details, and what is going on under the hood.
Glad it was helpful!
I'm a bit late to the party, but having now watched this video, I think I now feel pretty comfortable with using Git! That made a lot of sense! Thanks.
Awesome! I'm glad you were able to get a handle on it.
I have been using Git for couple of years for several projects, but this tutorial is an awesome one to learn some basic stuff. Great Job!!!
Thanks. I am glad you found it helpful.
Wow - Thank You! This really helped me use git better... even after years of being an independent dev, I can now work better with teams
Glad it helped!
Very big plus for clear explanation what are branches for and how actually use them!
I'm glad it was understandable. Branches are a big deal in git. You lose a lot of benefits of git if you don't know how to use them.
Great tutorial. Couldn't take my eyes of the screen for 90 min. I know there is much more to git, but his really helped me get started.
For the "git commit" command in 17:50:
If the notepad file does not open up and the same message appears in the console. press "esc" then type ":wq".
It is the same as saving and exiting the notepad file
Thanks for the suggestion.
Keep up the good work. For me Git was a mystery but good teachers always make mystery easy on eyes. Thanks a lot.
I think it is very good time to update this lesson to newest versions of Git and Visual Studio :) I would love to see it updated. And I think, that not only me.
Thank you. I have added this to Tim's list of possible future topics.
By far the best git tutorial on the web. Nice job bro
Thank you.
one of the best tutorials to be found on the internet. Super awesome super easy : cool
still the best video on git I have seen.
Thank you!
Nice job, Tim. The best I've seen yet. Thanks for taking the time to make such a clear explanation.
Fantastic Job Tim. Very helpful.
Great Tutorial. Best one I've seen so far.
Awesome!
Thank you Sir for posting this. Best Git tutorial on youtube.
I’m glad you enjoyed it.
Great video. I'm glad I opted to sit through this and try it out rather than skip it. Thanks :)
Excellent! I'm glad you enjoyed it.
Seriously good presentation, an exemplar of how tech training videos should be done
Thank you!
I can only repeat what others have said before me, great tutorial I'm using git from now on.
Excellent!
Tim once again excellent intro to git. I am sure you would have more indepth video on how to handle when there is clash. Thank you for sharing this.
More are coming.
Nice tutorial, very easy to understand. One suggestion would be to have some sort of visual representation of what is going on on the branches, their graph. Also, more info on resolving conflicts, and seeing the commit history inside git.
I'm working on a git course now. It will incorporate these suggestions. Thanks.
GIT is so powerful it's scary, but this video goes a long way toward ameliorating the fear. What are the best practices for preparing for a GIT failure of some kind? Do you have plans to do a more advanced video that will explain more about exactly how GIT performs this magic? (Or do you know of some existing ones?)
I don't have any videos yet but I intend to in the near future.
One of the best Git tutorials, thank you!
Thank you Tim for another fantastic tutorial. I was always mystified by Git before watching this. I will definitely be using it from now.
I am glad it cleared things up for you.
Hi Tim,
Thanks a lot for the tutorials. These are really helpful. Could you please create a detailed tutorial on working with Team Foundation Server (TFS) Source Control System specifically folder mapping, check out , checkin and merge process. Please share the link if there is already one.
Thanks.
I can add the suggestion to the list. I'm not sure if I will get to it or not. TFS is a style that is going away.
I watched plenty git tutorials in the last week or so, and this is probably the best so far.
Very simple explenations, very easy to understand, thank you very much!
Can you make a MVC 5 web app from start to finish video like you did the one on Win Form (Creating a C# Application: From idea to finished product) ?
I think that would be the best MVC 5 tutorial on youtube (and believe me, I think I watched them all :))
Once again, you are a great theacher, and I ask God One and Only to give all the best for you and your family.
All the best form Sarajevo, Bosnia and Herzegovina
+Timothy Corey This is great tutorial. I wish if you could make more C# example tutorials like the one Creating a C# Application: From idea to finished product. For example, how to make classes with other example, and maybe you could use grid control to display data. Note: Windows Forms are much better and easier to work with. Thanks
Always great content, many thanks Tim
You are welcome.
i wish i could say more than a THANK YOU, this is a perfect job done
You are welcome.
awesome tutorial, thanks a lot. Im completely new to all this and i was never lost.
Excellent ! Easy to understand .Very helpful for me.
Thank you Tim, very clear and detailed explanation. It just made my learning very easy.
Excellent!
Really amazing tutorial. It covers almost all the things and nicely explained. Really loved it..
I am glad you enjoyed it.
i can see you have upgraded you microphone quite a bit since then. tnx for the video. always good stuff :)
I try to continually improve.
Many Thanks, very good introduction. You are a very talented trainer!
Thank you!
This video is timless, very helpful.
Thank you!
Thanks a lot great descriptive and very good step by step explanation.
Very useful demo. Very good explanation
I'm glad you found it helpful.
Great work with this tutorial. You've got talent with this.
Thank you very much
+Timothy Corey Git Hub has BIG problem. It is not free. If you use Public repository and dont want to pay, than all can see your project. Why would someone work and give it for free?
Great video and excellent explanation, you are the best!
Tim -- Do you recommend using the source control features built into Visual Studio? As opposed to command line with Git Bash and /or UI such as GitHub Desktop?
I recommend learning the command line but then using the visual tools provided (in Visual Studio, standalone, etc.) There will be times you need to use the command line, plus knowing how the command line operates will help you better understand the GUI tools.
Great tutorial Timothy.
even from 2014 it still helps
Great!
It explains everything about git in detail, thanks
You are welcome.
You really do know how to teach...keep it up.
Thank you!
Thanks@Tim. Excellent tutorial 👌.
You are welcome.
Some update for 28:55, In Git version 2.15.0, it is able to add those deleted file by typing "git add ."
Thanks for the tip!
Very brilliantly done! Thank you very much!
You are welcome.
Brilliant Tutorial, really helped me a lot. Thanks
I'm glad the video was able to help you. Thanks for letting me know.
Thank you so much for making this video! It's tremendously helpful :)
commendable and soothing to understand
Great!
Hi Tim, Recently I have had to use SourceTree. Every time I realize I have to undo stuff after a commit (or after a few commits) and just go back to the state of the project at a certain revision, I assume that I can "simply roll back" because I use git (via SourceTree) but when I double click on any commit to check it out and take it from there, I always get a warning message that this action would create a detached head, etc... I have seen a lot of posts that deal with hard resetting, etc... but I wonder how would one just roll back without causing problems such as detached head then, and not having to reset all the previous commits? Thanks
I think the best option here would be to a "git checkout -b " That will create a new branch that only has up through the specified commit. I typically use the command line so I'm not sure how SourceTree does it but that command should help you out.
Great tutorial, thanks a lot Tim, really helped me. Could you comment on what Forks are and just mention the commands related with them? or Do you have a tutorial on them? Thanks a lot once again !
I don't have a tutorial on it, but forks are actually not too complicated. Essentially it is just a copy of a repository. So what you do is this: if you can see a repository but do not have access to make direct modifications (most of Github works this way), you make a fork (a copy of the repo onto your profile that you then have access to). From there, you can make changes to your copy. When you are finished making changes, you go to the original repository's site (the one you had read-only access to) and you make a pull request. Basically, a pull request is just a link to your repository and any notes you want to attach (like "I fixed bug 123 for you"). The owner of the original repository can then review your changes and merge them into their repository, they can ask you to make further changes, or they can reject your changes. That's all it is. Does that make sense?
Absolutely makes sense Tim, now I understand. Thank you very much for your prompt answer and your time, it is great ! I am sure that with your unique way of explaining things, you saved me some time here. Best regards.
After watching several tutorials,this is one of the best tutorials.Thanks for your clear explanation. but I have one doubt, if I have a software with multiple software versions, what should I do if I am going to use Git for versioning control, Should I put every earlier version as branches and the put current release as master?
The most common thing to do in this situation is to tag your releases (git-scm.com/book/en/v2/Git-Basics-Tagging). Essentially, whenever you are saying "this commit represents the last code to go out the door for this particular release" you add a tag. You don't need a new branch. So you have one branch but lots of tags that identify where the code was at each release point. If you needed to patch an older release without moving them to a newer release, you could check out that commit into a new branch and apply the patch. You could then merge that change into master or you could leave it alone.
Very nice, easy listening tutorial, well done, thanx
I am glad you enjoyed it.
Great Tutorial. Thank you for you time and you will be blessed (y)
You are welcome.
Excellent tutorial, great help, thanks a lot for sharing.
You are welcome.
Hi Tim, in your day life of developer, you use/prefer TFS or Git as souce control and build integrations?
Definitely git. Hands down. It is easier to work with, it is easy to maintain, and easy to move from one host to another. Plus, most of the industry uses it.
Thank you, this has been very useful to get me started.
I am glad I could help.
best teacher ever
Thanks!
Thank you as always for the great content.
You are welcome.
What a great teacher :)
Thanks!
This tutorial is truly awesome!
I am glad you found it so helpful.
Is it common practice to delete finished branches? Are there any cons to doing so?
Yes it is an there usually isn't a con to it. Once you have merged your changes into master, you can safely delete the branch because you haven't lost anything. Everything is in master. The only dangerous thing is if you delete a branch that has not been merged into master (or another branch). Then those changes will be gone and there isn't a good way to get them back (there is a possibility of getting a deleted branch back but you shouldn't plan for it).
Around 17:30 where you explain git commit I get an error.
Gvim is my text editor, and it opens up after typing "git commit", but I also see "Aborting commit due to empty commit message." and a new line "(gvim:21814): GLib-GObject-WARNING **: cannot retrieve class for invalid (unclassed) type ''"
I'll study that to solve the error, thanks.
thx for your work but need here little help im starting new c# and i dont know what video of yours should i start can you just point me at the right path to begin
Start here: Full C# Tutorial Path for Beginners and Everyone Else (th-cam.com/video/LUv20QxXjfw/w-d-xo.html)
1:18:16 Something like that is better visualized on GitHub. On Line 2 you added a Line Break to it, before that is was EOF ;)
Back then GitHub didn't offer free private repos like BitBucket did, which is why I demonstrated it on BitBucket. Now I would probably use Azure DevOps.
Is it possible to use git commands in normal cmd? I've seen some tutorials using the Windows cmd without using the git CLI.
Is Cygwin not such a tool?
Excellent explanation. When I do git push -u origin master nothing happens and the cmd seems to "freeze". What can be happening? (I have to do Ctrl + C to cancel)
Do you actually have an origin set up?
@@IAmTimCorey Yep
Thanks for clean explaination
You are welcome.
When committing for the first time 16:36 if you get the following error:
fatal unable to auto-detect email address .
You can solve this by setting your email address by typing:
git config --global user.email "you@example.com"
Then try committing again and it should work.
Thanks for sharing.
Is this still a relevant resource for learning GIT?
Because it is from 2014
Thank you in advance,
Vasko
Absolutely. The commands are all still the same.
You are the best. Thanks for this
You are welcome.
Best git tutorial! Thanks!
You are welcome.
You are a gem man.
Thanks!
Amazing video! Thank you!
You are welcome.
Kindly Make a tutorial of Git for Visual Studio with Github
I will add it to the list. Thanks for the suggestion.
Ok I get it, Git is designed to be obfuscated and to seem needlessly more complicated than it needs to be. The question is, what is a good alternative to not having to deal with Git?
It isn't designed to be obfuscated or to seem complicated. Actually, once you understand what it is doing, most of the commands are incredibly intuitive. However, what it is doing is incredibly complex so sometimes there are complex things you need to do to make it do what you want. As for the alternatives, Git is the industry standard. You need to know it if you want to be viable in the market. There are definitely places that don't use it, but they are quickly becoming the minority. Besides, Git is the best solution for source control we have and source control is imperative.
I have some problem, I couldn't find the solution on the web. I want Git to load my repository automatically after Git starts. How can i set that?
I am not sure what you are looking to do. The phrase "after Git starts" is interesting. Git doesn't really run. It just sits there until you call it. So for example, if I open up git bash at the root of my project, that is essentially just a command prompt. In fact, my command prompt acts just like the git bash. It is only when I issue a command like "git status" that git is called and it does something.
You could do a batch statement so that when you called a certain command, multiple git commands are issued at once but I don't see that as helpful. For instance, if you want to be sure that your local copy of the repository is up to date with the remove version, you would want to run a few commands but you need to make decisions based upon the results. For instance, I would first start with "git status" to identify the state of my local repo. If I have uncommitted files, I would then run a commit command or a stash command, depending on what I wanted to accomplish. If there were no uncommitted files (or after I had handled them), I would run a "git pull". That would bring in the commits from the remote repo and it would merge the changes with my local commits. If there were differences that caused a merge conflict, I would need to deal with those issues next and create a merge commit. As you may notice, none of these steps should be done blindly. That is why the git tools out there don't do these tasks automatically and why you cannot find out how to do this yourself.
If I misunderstood your question or if you have further questions, please let me know.
I've looked and looked, and can't get passed this error when trying to push for the first time with . I replace "origin" with my repository name . Here is the error I keep getting when trying to push: Updates were rejected because the tip of your current branch is behind its remote counterpart. Integrate the remote changes.
Any ideas?
It seems as though your remote branch has been updated since your local branch was updated. Do a "git pull" first and merge the changes locally, then do your "git push".
IAmTimCorey - yep, that worked. Thank you, Tim!
If any can help! How can i "Push" new branches to the remote "origin"? In git-demo if i create new branch "Dev" how can i push dev branch to to remote repo?
If you have set your origin as your default upstream (this happens by default if you clone from a repo) then you would just do a "git push". If you have not set it as your default upstream, you would do a "git push origin dev" to push to the dev branch of origin (even if it doesn't exist yet).