Closed jasonmesser7 closed 2 years ago
Well I broke the feature branch rule in that my README commit is not relevant to the feature here. Ignoring that the two commits are valuable in isolation and so I would commit without squashing on this one.
Technically we should cherry pick and make the README a separate PR. But it is inconsequential (I actually only did it to ensure Git was going to let me commit after I changed my Git user).
I'll just go ahead and merge.
@rgardler-msft Changes look good to me. In this case should we squash and merge or create a merge commit?