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.

Sign up for GitHub

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

Jump to bottom

Notifications #61

Closed
eregon opened this issue Apr 14, 2015 · 2 comments
Closed

Notifications #61

eregon opened this issue Apr 14, 2015 · 2 comments

Comments

@eregon
Copy link
Member

eregon commented Apr 14, 2015

Now that Travis is green again #55 (comment),
I think we should enable notifications when the build is broken.
Of course there will be false negatives if the change applies on trunk but Travis's trunk is not yet updated. But it would be quite good for any other change.

Who wants to get notified? The committer and author, Travis' default?
@eregon
Copy link
Member Author

eregon commented Apr 14, 2015

And similarly for MSpec, with the advantage of no false negatives.

@eregon
Copy link
Member Author

eregon commented May 27, 2015

The default notifications have been adopted, so the commit author will receive an email if the build fails or fixed the build. See 72e4b19. MSpec already has the default notifications enabled.

@eregon eregon closed this as completed May 27, 2015
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eregon