Don't start forming a negative perception of Git, tempting though this is! I had Git and Github dumped on me two years ago and had little help from coworkers back then, I tried very hard to get a solid grasp of it and it took me months, but after all that I can now tell you are using a very solid and robust system, almost all issues you'll have stem from wrong perceptions or a poor workflow, and this is only natural given how poor the materials are for learning Git.
SmartGit is a very good way to learn and work with Git too, so despite being confused and bewildered you're using two very solid technologies, I'm now novice either, been a develop since late 1970s. Now take a quick look at a post I made recently to StackOverflow, it sumarrizes a Git workflow that I've defined for all developers here to work with. http://stackoverflow.com/questions/14865283/proper-git-workflow-scheme-with-multiple-developers-working-on-same-task/41753291#41753291 Understanding this (and similar) workflows is the best way to then understand the lower level details, approaching Git basics without understanding the bigger picture will probably be more confusing. Regarding your picture, you need to understand that a pull-request (until its approved (merged)) is a branch level request, that is it's a request to move ALL commits on one repo/branch to some other repo/branch. If at the time you create a pull-request there are five commits in your branch then a few days later you push and additional three commits to your branch, the pull-request will "see" these additional commits and report eight commits in the (still pending) pull-request. Your picture suggests that after you pushed additional recent commits, these (in some way) undid some of the hundreds of changed files in the original commits, which may have been intentional? On Monday, January 16, 2017 at 4:33:52 PM UTC-7, AD S wrote: > > Hi all, > > I decided to screen shot one of these issues I'm encountering. This is a > kind of small one. > > I've been styling a site - just .scss files. I pushed to Github at the end > of the day and saw I had 400+ files that I had apparently altered and > merged to the branch. This isn't true - I'd only worked on a handful of > files. I spent a few hours trying to figure out why this was before giving > up and continuing with my styling (remembering to also manually save a > local copy of the files I was working). When I returned today to look at > the branch and try to address the problem again, I see that it is back to > normal. > > I don't know why the branch suddenly contained a few hundred more files > than I was working on our why it now suddenly doesn't. This was a lucky one > - it fixed its self. > > > <https://lh3.googleusercontent.com/-HxUl0OZ8NMk/WH1YTyooBLI/AAAAAAAAAJ4/5Sv16qoiKPAKuLFG9RYpePo7folI70l8QCLcB/s1600/issue.png> > > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
