weex-bot removed a comment on issue #2768: Feature/new log branch URL: https://github.com/apache/incubator-weex/pull/2768#issuecomment-517105236 <!-- 0 failure: 6 warning: If your PR is abo..., Current pr not bi..., No Changelog chan..., Potential BREAK C..., Potential BREAK C..., Potential BREAK C... 1 messages --> <table> <thead> <tr> <th width="50"></th> <th width="100%" data-danger-table="true">Warnings</th> </tr> </thead> <tbody><tr> <td>:warning:</td> <td>If your PR is about fixing a bug excluding crash the code,you should add the demo link in the PR description. here is a demo link:http://dotwe.org/vue?spm=a2c7j.-guide-contribute-contribute-code.0.0.3e93748cmxz3yt</td> </tr> <tr> <td>:warning:</td> <td>Current pr not bind the milestone</td> </tr> <tr> <td>:warning:</td> <td>No Changelog changes! - <i>Can you add a Changelog? To do so,append your changes to the changelog.md</i></td> </tr> <tr> <td>:warning:</td> <td>Potential BREAK CHANGE. Modify public in android/sdk/src/main/java/com/taobao/weex/WXEnvironment.java without metion it in commit message. You'd better add '@notdanger' in your commit log. </td> </tr> <tr> <td>:warning:</td> <td>Potential BREAK CHANGE. Modify public in android/sdk/src/main/java/com/taobao/weex/bridge/WXBridgeManager.java without metion it in commit message. You'd better add '@notdanger' in your commit log. </td> </tr> <tr> <td>:warning:</td> <td>Potential BREAK CHANGE. Modify public in android/sdk/src/main/java/com/taobao/weex/bridge/WXBridge.java without metion it in commit message. You'd better add '@notdanger' in your commit log. </td> </tr> </tbody> </table> <table> <thead> <tr> <th width="50"></th> <th width="100%" data-danger-table="true">Messages</th> </tr> </thead> <tbody><tr> <td>:book:</td> <td>danger test finished.</td> </tr> </tbody> </table> <p align="right"> Generated by :no_entry_sign: <a href="http://github.com/danger/danger-js/";>dangerJS</a> </p>
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
