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

Adding test error #1

Closed
wants to merge 1 commit into from
Closed

Adding test error #1

wants to merge 1 commit into from

Conversation

bluzi
Copy link
Owner

@bluzi bluzi commented Dec 2, 2017

No description provided.

bluzi added a commit to bluzi/cube-ui that referenced this pull request Dec 2, 2017
TravisBuddy will comment on pull requests in your public repository everytime a test failed in one of them. The comment will include only the part of the build log that applies to your testing framework, so your contirbutors won't have to enter Travis's website and search the long and annoying build log for the reason the tests failed.

Here's an example: bluzi/express#1
bluzi added a commit to bluzi/remotestorage.js that referenced this pull request Dec 2, 2017
TravisBuddy will comment on pull requests in your public repository everytime a test failed in one of them. The comment will include only the part of the build log that applies to your testing framework, so your contirbutors won't have to enter Travis's website and search the long and annoying build log for the reason the tests failed.

Here's an example: bluzi/express#1
bluzi added a commit to bluzi/ganon that referenced this pull request Dec 2, 2017
TravisBuddy will comment on pull requests in your public repository everytime a test failed in one of them. The comment will include only the part of the build log that applies to your testing framework, so your contirbutors won't have to enter Travis's website and search the long and annoying build log for the reason the tests failed.

Here's an example: bluzi/express#1
bluzi added a commit to bluzi/jsonplaceholder that referenced this pull request Dec 2, 2017
TravisBuddy will comment on pull requests in your public repository everytime a test failed in one of them. The comment will include only the part of the build log that applies to your testing framework, so your contirbutors won't have to enter Travis's website and search the long and annoying build log for the reason the tests failed.

Here's an example: bluzi/express#1
bluzi added a commit to bluzi/kraken-js that referenced this pull request Dec 2, 2017
TravisBuddy will comment on pull requests in your public repository everytime a test failed in one of them. The comment will include only the part of the build log that applies to your testing framework, so your contirbutors won't have to enter Travis's website and search the long and annoying build log for the reason the tests failed.

Here's an example: bluzi/express#1
bluzi added a commit to bluzi/dpl that referenced this pull request Dec 2, 2017
TravisBuddy will comment on pull requests in your public repository everytime a test failed in one of them. The comment will include only the part of the build log that applies to your testing framework, so your contirbutors won't have to enter Travis's website and search the long and annoying build log for the reason the tests failed.

Here's an example: bluzi/express#1
bluzi added a commit to bluzi/Vim that referenced this pull request Dec 2, 2017
TravisBuddy will comment on pull requests in your public repository everytime a test failed in one of them. The comment will include only the part of the build log that applies to your testing framework, so your contirbutors won't have to enter Travis's website and search the long and annoying build log for the reason the tests failed.

Here's an example: bluzi/express#1
@bluzi bluzi closed this Dec 2, 2017
bluzi added a commit to bluzi/bulma that referenced this pull request Dec 2, 2017
TravisBuddy will comment on pull requests in your public repository everytime a test failed in one of them. The comment will include only the part of the build log that applies to your testing framework, so your contirbutors won't have to enter Travis's website and search the long and annoying build log for the reason the tests failed.

Here's an example: bluzi/express#1
dolymood pushed a commit to didi/cube-ui that referenced this pull request Dec 4, 2017
TravisBuddy will comment on pull requests in your public repository everytime a test failed in one of them. The comment will include only the part of the build log that applies to your testing framework, so your contirbutors won't have to enter Travis's website and search the long and annoying build log for the reason the tests failed.

Here's an example: bluzi/express#1
BlakeGuilloud pushed a commit to BlakeGuilloud/ganon that referenced this pull request Dec 4, 2017
TravisBuddy will comment on pull requests in your public repository everytime a test failed in one of them. The comment will include only the part of the build log that applies to your testing framework, so your contirbutors won't have to enter Travis's website and search the long and annoying build log for the reason the tests failed.

Here's an example: bluzi/express#1
Repository owner deleted a comment from TravisBuddy Apr 1, 2018
@bluzi bluzi reopened this Apr 1, 2018
@bluzi bluzi closed this Apr 1, 2018
Repository owner deleted a comment from TravisBuddy Apr 1, 2018
hu0950 pushed a commit to didi/cube-ui that referenced this pull request Nov 1, 2019
TravisBuddy will comment on pull requests in your public repository everytime a test failed in one of them. The comment will include only the part of the build log that applies to your testing framework, so your contirbutors won't have to enter Travis's website and search the long and annoying build log for the reason the tests failed.

Here's an example: bluzi/express#1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant