The "readme generated after latest change" check fails on travis
raimohanska opened this issue · comments
Juha Paananen commented
The "readme generated after latest change" check fails on travis
Juha Paananen commented
Disabled the check temporarily in ce7d33e
Juha Paananen commented
Here's a snippet from the log https://api.travis-ci.org/v3/job/467700572/log.txt
diff --git a/README.md b/README.md
index 5477c49..de56bcd 100644
--- a/README.md
+++ b/README.md
@@ -1796,7 +1796,7 @@ latter is for observable properties that have the concept of "current value".
Also, there are no "cold observables", which
means also that all EventStreams and Properties are consistent among subscribers:
-when as event occurs, all subscribers will observe the same event. If you're
+when an event occurs, all subscribers will observe the same event. If you're
experienced with RxJs, you've probably bumped into some wtf's related to cold
observables and inconsistent output from streams constructed using scan and startWith.
None of that will happen with bacon.js.
travis_time:end:02e0ae14:start=1544733466205074141,finish=1544733466993640085,duration=788565944
�[0K�[31;1mThe command "npm run readme && git diff --exit-code README.md" exited with 1.�[0m