Prior to staging them, I wish to see that what I changed in my current working directory (that is the current working folder) compares with the staged changes. Just continue to travel with me and pause on this for a few seconds. Can you guess why? If you can't, that's completely fine. Then, let's say I want to make some changes to the dog's name – like I wish to call it "pup" instead of "puppy".īefore that, if I run the git diff command, it shows nothing. Want to confirm? Then use git status, which shows which changes are ready to commit like below: Then we move this change to the staging area using git add cat.txt dog.txt. They introduce themselves with their names – like this: No, it's not a formal repo, but it's quite serious 😉. Let's take an example: I created a Git repository which is cat_vs_dog. Git diff lists out the changes between your current working directory and your staging area. Just start to read the article cheerfully. I know you're probably concerned with your time, so let's get this ride on the road.Īnd don't worry – I will teach you each command with a fun example. Fortunately, you can verify all this using the Git diff command. These are common issues and tasks when working with a version control system. Perhaps you want to see the differences between two branches, commits, or files. Or maybe you want to see what changes you're going to commit compared to your last commit. Hey friends, have you ever been working in Git and found yourself wondering if you're going to stage the correct changes?
0 kommentar(er)
