Skip to content

Conversation

Havvy
Copy link

@Havvy Havvy commented Aug 20, 2018

I'm not quite sure this can be merged directly to update the PR, or if you have to do some semi-complicated git commands to get it right, but I've rebased against master and then sent in a new commit to fix the things I noticed when I first reviewed the PR.

@alercah alercah force-pushed the upgrade branch 4 times, most recently from 0444157 to a852878 Compare February 2, 2019 17:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant