Hi Harry, Both behaviours you report are normal, specifically: On 09/05/2017 15:02, Harry Putnam wrote: > Shouldn't files that changed but are already being tracked just show > up as modified and not need adding? > ... > Since that file is already being tracked; shouldn't `git status' show > that file as modified but ready to be committed instead of a file that > is modified but needs to be added before a commit can happen? No, it shouldn`t - even though the file you`ve modified is already being tracked, it doesn`t have to mean you want the modification inside your very next commit, and Git doesn`t force that upon you. That is where index (or "staging area") comes in handy, allowing you to `git add` only the changes you actually want to commit now, leaving the others for later decision. You don`t even have to add all the modifications inside the single file at once, for example by using `git add --patch`[1] you can select just some of the them, fine tuning what gets committed and when. With some precaution/steps needed not to commit broken project states by accident, and some discipline not to overdo it, this allows you to fully focus on the actual work you do, making logically unrelated changes in place as you see fit, on the go, and only later organizing them into logically grouped commits, through diligent use of `git add`. > Another side of this is that a `git diff FILE' only works before an > `git add .' operation is done. > > That is, if I run `git diff FILE' AFTER `git add' .. no diff is > reported, even though it is not committed yet. > > So, for example: if I'm committing and in the vi buffer of the commit > and want to see a diff of FILE to aid my log notes. > > git diff FILE will report nothing whatever. > > Is that expected behavior? Yes, that is as expected - in the form you`ve given, `git diff` shows the differences between your working tree and index (staging area), so only changes you haven`t added yet. Once you `git add` the changes from the working to the index, there are no more differences to show, so no diff is produced. If you want to see the added changes, what will be included in the commit if you make it, you can use `git diff --cached`, as per git-diff[2] documentation (--staged can also be used instead, being a synonym for --cached, but maybe easier to remember, relating it to "staging area"). That option shows differences between the staging area (index) and the specific commit - with none provided, it implies your currently checked-out position (referred to as HEAD), usually being your latest/previous commit, which is exactly what you`re interested in. As a side note, if you think you don`t need it, you can skip staging area and commit all the modifications/deletions without a need of adding them first by using `git commit --all`, as per git-commit[3] documentation. Just pay attention that untracked files are not affected, you still need to add them first to tell Git to start tracking them, including them in the next commit, but that seems to align nicely with your expectations already. I personally find the staging area to be one of the greatest Git possibilities, but I do understand beginners getting confused by it, as admittedly I once was myself. In the end, you may want to ask questions like this on Git users mailing list[4] on Google Groups, being a a nice place for beginners to get answers to their concerns. [1] https://git-scm.com/docs/git-add [2] https://git-scm.com/docs/git-diff [3] https://git-scm.com/docs/git-commit [4] https://groups.google.com/forum/?fromgroups#!forum/git-users Regards, Buga