Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/6983#issuecomment-116863918
+1 to @squito 's suggestion, and I'll add that you can also force push if
you do a rebase instead of a merge. Eitherway, github only is going to look at
whatever the head commit of the branch you used to open this PR. When we merge
to spark master we have a script that squash commits, so it doesn't really
matter if the tree is messy. There will only be one clean commit no matter
what the PR looks like.
I should be able to look at it this week (and I've marked myself as the
shepherd on JIRA so it should show up on my dashboard when its ready).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
