[Request] Use encrypted email in Travis-CI notification to avoid spam from forks

[screw]

Would you consider to use encrypted email in Travis-CI settings for notifications to avoid getting spam from forked repositories?

Reference: https://github.com/travis-ci/travis-ci/issues/5063#issue-115477841 https://github.com/facebook/flow/pull/1822

[torokati44]

Nice find, thanks! A bit hacky, but if it works... Then again, our Travis config is exceedingly cursed already.

[torokati44]

Let's wait for an e-mail notification to arrive before closing this issue (this will most likely only happen next when some tests fail), just to confirm that decryption works, and I haven't made a mistake in the glorious YAML syntax.

[torokati44]

This change has been in the mainline master for quite some time now, and also in @screw's fork a couple times, but not in all branches yet. If a build is triggered in a fork, on a branch/tag/hash that does not include this change, we will still get the notification about it.

[screw]

Did I do that again?!?

[torokati44]

Yep, a couple times, last week, on the topic/ipsec branch. No problem though! :)

[levy]

Can we close this issue?

[torokati44]

Yes, as we don't even use Travis CI for INET anymore.