:octocat: GitHub to Twitter hook glue
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.gitignore
Gemfile
LICENSE
README.md
config.yml
gwitter.rb

README.md

gwitter

License: GPL v3

GitHub to Twitter hook glue

Gwitter is primarily being written for use with the SEGS Project for Twitter and Discord notifications. As such, only pull request/merge and release events are currently handled considering the needs of the aforementioned project. You will need to manually handle other specific event types that you want posted to Twitter as a result. Support for more events will likely be added for posterity at some point. For a list of available events supported by the GitHub API, please see the following:

Gwitter requires the use of Twitter consumer and access tokens for authentication and authorization. These can be procured after creating a Twitter application at: https://apps.twitter.com/

For added security, you can optionally:

  • Permit traffic on your firewall for just the hook networks referenced here: https://api.github.com/meta

  • Generate a GitHub hook secret for validation using:

ruby -rsecurerandom -e 'puts SecureRandom.hex(20)'

  • Make use of SSL certificates which can be generated using Let's Encrypt or another CA. You may also generate self-signed certificates using:

openssl req -x509 -nodes -newkey rsa:2048 -keyout server.key -out server.crt -days 365

Note: If you are utilizing self-signed certificates, you must disable SSL verification for the GitHub hook.

Gwitter has the following requirements: