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

[10.0][FIX] help_online: Restore commit history and remove bug introduced at merge time #647

Merged
merged 4 commits into from
Jun 1, 2017

Conversation

lmignon
Copy link
Contributor

@lmignon lmignon commented Jun 1, 2017

Reverts #584
The commit history is not honored and a commit added to the initial branch at merge time by @yajo breaks travis.

@dreispt Can you merge this one ASAP?

@lmignon
Copy link
Contributor Author

lmignon commented Jun 1, 2017

@dreispt I've restored the initial state of #584
This branch can be fast tracked since the commits are approved by 5 reviewers.

@lmignon lmignon changed the title Revert "[10.0] help_online fix export/import" [10.0][FIX] help_online: Restore commit history and remove bug introduced at merge time Jun 1, 2017
@pedrobaeza
Copy link
Member

What is the problem, Laurent?

@lmignon
Copy link
Contributor Author

lmignon commented Jun 1, 2017

@pedrobaeza
At merge time of #584, @yajo has added a new commit that breaks travis!
image

Moreover
The 3 commits have been squashed into one and the authorship is not honored. I'M NOT THE AUTHOR OF THIS 💣 COMMIT and my commit history was clean and should not have been squashed.
image

@yajo
Copy link
Member

yajo commented Jun 1, 2017

Yeah, bug fault of mine. Travis was down due to #ocacodesprint and I wanted to fix #584 (comment) to merge quickly.

Also I did not mind on authorship of such a small change and that's why I squashed.

In any case, I added the fix here now, but we'll wait for Travis this time 😋. Thanks!

@yajo yajo self-assigned this Jun 1, 2017
@yajo yajo added this to the 10.0 milestone Jun 1, 2017
@yajo
Copy link
Member

yajo commented Jun 1, 2017

OK, all ✔️, fast-tracking. Thanks @lmignon! (And sorry again 😅)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants