Staging and Git

A simple gotcha when woring with Git

Evaldas Landauskas asked a question on some missing code when using Git so I thought I'd walk through a common "gotcha" when using Git, if you've not had this issue before. First, we're going to start with this repo: https://github.com/NathanClouseAX/AAXPOCloseHelper

In order to setup the problem, I'll have to clone it locally and setup a branch to create the issue described. I'll clone the repo to C:\AOSService\PackagesLocalDirectory\AAXPOCloseHelper ( this is an Environment VHD ) then get everything setup. 

Added developer branch: https://github.com/NathanClouseAX/AAXPOCloseHelper/tree/developer

Published It

Open the VS solution for this then when to Changes and confirmed I have nothing there.

next, I'm going to add a runnable class just as an example.

Notice the green plus sign next to my new "RunnableClass1". That means Source Control, in case Git, sees it. However, Source Control may need some additional info on what to do. Next, lets go back to out changes window.

You can see what have changes but nothing to commit. We have to select what changes we want to stage for commit with the plus button.

Now I can commit everything, including my new file. However, from personal experience, if I leave an edit to a file locally unstaged and I get an update in the branch i'm in from a pull request, i'll get an error that I have local changes that must be deleted. If you have any questions, please let me know.