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

IRC spamming from github forks problem solved \o/ #5063

Closed
petemoore opened this issue Nov 6, 2015 · 2 comments
Closed

IRC spamming from github forks problem solved \o/ #5063

petemoore opened this issue Nov 6, 2015 · 2 comments

Comments

@petemoore
Copy link

I wanted to update #1094 to advise that there is a very neat solution, but unfortunately issue 1094 has been locked so that I can't post to it.

However, here is the solution for the many people that are still interested in this topic.

Simply secure the channel name, like so:
mozilla/build-tools@c13a297

Please can issue 1094 be unlocked to have this information added to it directly?

Many thanks,
Pete

@petemoore
Copy link
Author

@roidrage See above. Thanks.

@BanzaiMan
Copy link
Contributor

I updated #1094 as requested.

ghost pushed a commit to facebook/flow that referenced this issue May 20, 2016
Summary:
Based on a trick found here: travis-ci/travis-ci#5063 (comment)

Long story short, `travis encrypt -r "facebook/flow" "flowtype@fb.com"` creates a value that is only decrypted properly in the `facebook/flow` repo. This way, the email and IRC notifications only work for `facebook/flow` and not for the GitHub forks.
Closes #1822

Reviewed By: mroch

Differential Revision: D3328300

Pulled By: gabelevi

fbshipit-source-id: 5fcaebe36f6ca7eafb7ebefd9908ad31ed3329dc
jberry-suse added a commit to jberry-suse/openSUSE-release-tools that referenced this issue Nov 29, 2018
Rather silly there is not better solution, but as noted by others this is
the only relatively sane way to do it.

- travis-ci/travis-ci#1094
- travis-ci/travis-ci#5063
- mozilla/build-tools@c13a297
nilxam pushed a commit to nilxam/osc-plugin-factory that referenced this issue Nov 29, 2018
Rather silly there is not better solution, but as noted by others this is
the only relatively sane way to do it.

- travis-ci/travis-ci#1094
- travis-ci/travis-ci#5063
- mozilla/build-tools@c13a297
justinmayer added a commit to getpelican/pelican that referenced this issue Aug 23, 2019
myii added a commit to myii/ssf-formula that referenced this issue May 20, 2020
* Use `%2F` for the forward slash in the topic name:
  - https://docs.travis-ci.com/user/triggering-builds/
  - https://www.degraeve.com/reference/urlencoding.php
* Use Travis `if` conditional rather than `secret` encrypted enviroment
  variable workaround suggested:
  - Not a secret, just the bot's API key
  - Need to be able to modify parts of the URL in certain situations,
    such as the weekly `master` branch tests
  - References:
    + https://docs.travis-ci.com/user/environment-variables/#encrypting-environment-variables
    + travis-ci/travis-ci#329
    + travis-ci/travis-ci#1094
    + travis-ci/travis-ci#5063
    + travis-ci/travis-ci#6100
    + mozilla/build-tools@c13a297
myii added a commit to myii/ssf-formula that referenced this issue May 20, 2020
* Use `%2F` for the forward slash in the topic name:
  - https://docs.travis-ci.com/user/triggering-builds/
  - https://www.degraeve.com/reference/urlencoding.php
* Use Travis `if` conditional rather than `secret` encrypted enviroment
  variable workaround suggested:
  - Not a secret, just the bot's API key
  - Need to be able to modify parts of the URL in certain situations,
    such as the weekly `master` branch tests
  - References:
    + https://docs.travis-ci.com/user/environment-variables/#encrypting-environment-variables
    + travis-ci/travis-ci#329
    + travis-ci/travis-ci#1094
    + travis-ci/travis-ci#5063
    + travis-ci/travis-ci#6100
    + mozilla/build-tools@c13a297
myii added a commit to myii/ssf-formula that referenced this issue May 21, 2020
* Use `%2F` for the forward slash in the topic name:
  - https://docs.travis-ci.com/user/triggering-builds/
  - https://www.degraeve.com/reference/urlencoding.php
* Use Travis `if` conditional rather than `secret` encrypted enviroment
  variable workaround suggested:
  - Not a secret, just the bot's API key
  - Need to be able to modify parts of the URL in certain situations,
    such as the weekly `master` branch tests
  - References:
    + https://docs.travis-ci.com/user/environment-variables/#encrypting-environment-variables
    + travis-ci/travis-ci#329
    + travis-ci/travis-ci#1094
    + travis-ci/travis-ci#5063
    + travis-ci/travis-ci#6100
    + mozilla/build-tools@c13a297
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants