Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tracking: Fix in-flight collision of two related PRs #2867

Merged
merged 1 commit into from
Sep 26, 2017

Conversation

dlespiau
Copy link
Contributor

Unfortunately, I forgot to rebase before renaming trackMixpanelEvent() and a PR
adding a new trace point was already in-flight.

More precisely:

Each PR is fine, but with the merge of both without rebasing any, we end up
with master having a dandling call to trackMixpanelEvent().

@dlespiau dlespiau requested a review from aaron7 September 26, 2017 10:14
Copy link
Contributor

@aaron7 aaron7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm 👍

Unfortunately, I forgot to rebase before renaming trackMixpanelEvent() and a PR
adding a new trace point was already in-flight.

More precisely:
  - #2861 renames trackMixpanelEvent()
    to trackAnalysticsEent()
  - #2857 add a new
    trackMixpanelEvent() call.

Each PR is fine, but with the merge of both without rebasing any, we end up
with master having a dandling call to trackMixpanelEvent().
@dlespiau dlespiau force-pushed the 2017-09-26-mixpanel-cleanup.2 branch from c53f05a to 53f1890 Compare September 26, 2017 11:59
@dlespiau dlespiau merged commit 46c5fca into master Sep 26, 2017
@dlespiau dlespiau deleted the 2017-09-26-mixpanel-cleanup.2 branch September 26, 2017 12:36
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.

2 participants