Closed baumatron closed 7 years ago
Do we have opinions on whether I should squash and merge or do a merge commit for this? I like to use many logical commits to make the review easier to follow, but not sure if that history is useful to keep around once the topic branch is blown away.
Whatever you think is a logical/meaningful set of commits.
I'd prefer at least a merge commit, but "Squash & Merge" will actually fast forward which I'm against.
Oh and It'd be nice to merge the Travis CI change first.
Lol. I removed some unnecessary code and added some constants so code coverage went down. Oh well.
Post merge build from my fork: https://travis-ci.org/baumatron/keen-sdk-net/builds/260398765
Fix #108