Track tasks and feature requests
Join 36 million developers who use GitHub issues to help identify, assign, and keep track of the features and bug fixes your projects need.
Sign up for free See pricing for teams and enterprisesTravisBuddy #3722
Comments
This comment has been minimized.
This comment has been minimized.
stale
bot
commented
Dec 26, 2018
|
This issue hasn't seen any activity in the past 30 days. It will be automatically closed if no further activity occurs in the next two weeks. |
stale
bot
added
the
waiting
label
Dec 26, 2018
rmzelle
added
the
pinned
label
Dec 27, 2018
stale
bot
removed
the
waiting
label
Dec 27, 2018
rmzelle
added
repository
quality-control
labels
Dec 27, 2018
rmzelle
referenced this issue
Apr 26, 2019
Open
For failing tests, add messages based on specific test failures #14
This comment has been minimized.
This comment has been minimized.
|
Given @retorquere 's current work and our limited success with this, I'm going to close it. |
adam3smith
closed this
Jun 7, 2019
This comment has been minimized.
This comment has been minimized.
retorquere
commented
Jun 7, 2019
•
|
I did look at Travis buddy, but
So all in all it didn't seem to me to be worth going that route. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
rmzelle commentedOct 2, 2018
I came across https://www.travisbuddy.com/, which appears to be the most popular GitHub/Travis-CI bot.
It seems a bit more advanced than our current https://github.com/citation-style-language/Sheldon tool, as it can leave comments directly in the pull request with Travis build summaries. See https://github.com/bluzi/travis-buddy, as well as bluzi/travis-buddy-jasmine-tests#2 (comment) for a real example. I find the regular Travis build webpages rather intimidating to newcomers, so this seems like it would be a big improvement.