When you are getting set up with using GIT for data science work you will likely have some teething issues with getting your process and flow right.
One common one is that you have a GIT repo that controls your production code, but you make config changes in the prod code, and code changes in your working copy. If you have not graduated to PULL requests from DEV branches, then you might find yourself unable to push changes made without merging into PROD.
Here are some small things that are useful in understanding what has changed before you flick that switch.
Look at what the commits are that not in your current working version
git log HEAD..origin/master
This will give you something like
commit 30d1cb6a3564e09753078288a9317f1b2309ab81
Author: John Hawkins <johawkins@blahblahblah.com>
Date: Tue May 23 10:03:10 2017 +1000
clean up
commit d69a1765bcfa4257573707e9af2bb014c412d7d8
Author: Added on 2016-12-06i <johawkins@blahblahblah.com>
Date: Tue May 16 05:39:14 2017 +0000
adding deployment notes
You can then inspect the changes in the individual commits using:
git show --pretty="" --name-only d69a1765bcfa4257573707e9af2bb014c412d7d8
Which will give you something like
commit d69a1765bcfa4257573707e9af2bb014c412d7d8
Author: Added on 2016-12-06i <johawkins@blahblahblah.com>
Date: Tue May 16 05:39:14 2017 +0000
adding deployment notes
drill_udfs/README.md
Note that it will show you the changed files at the end, which is often the most important thing to know. At least this help me understand what I am bringing in.
