-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Remove email notifications from all Travis setups? #40
Comments
I wouldn't mind, esp. with all the random failures lately. It's crazy |
Also I used to rely on these emails for progress updates but now I just look at the project board. |
Maybe we could use a level-mail which redirects? I have a feeling it's causing quite a lot of spam for people in @Level/core |
Sure, we could send it to |
@ralphtheninja I'm gonna start disabling notifications, in the noisiest repos. Without email forwarding. Note that Travis only sends emails to the committer and the author so other people aren't spammed. But we (active maintainers) are. There are maybe a few scenarios where notifications are useful, but those notifications currently get lost in the noise anyway. |
This comment has been minimized.
This comment has been minimized.
Done. |
- Add nyc & coveralls for code coverage (Level/community#34) - Add engines.node to package.json (minimum is now 8) - Disable Travis notifications (Level/community#40) - Bump dependencies to prevent dedupe - Add faucet to format test output - Add dependency-check
Also, do we really need
sudo: false
anymore?The text was updated successfully, but these errors were encountered: