Closed wking closed 7 years ago
yep :) merged
It looks like this is racy. The last merged PR was #44, and the master build on 13:43Z was using the right commit (258ef80c) and deployed main.e23aaba6.js
. But the gh-pages commit (41aaa1f, committed 13:43Z) has main.fab81fbe.js
. That looks like it's from the previous build, which started a few seconds earlier but ran almost a minute longer. I'm not sure what the runtime difference is; maybe #46 will help make things more consistent. Until then, we might need to push manual builds if PRs are merged too close together.
@jbenet - Hu Juan, In our organization we have separate business unit dedicated to work on emerging technologies and we would like you to be part of one of the speaker in guest speaker series for an hour to provide insight on IPFS. Let me know if you are interested in it and how can we reach out to you to work on the schedule. Sorry for using this post for this purpose. Thanks !!
Background in #40. I expect this will work, but the target-branch clause means we won't know until this PR gets merged. If it is broken, I expect a few fixup commits while we get it right won't be a big deal.
Fixes #40.