github2fedmsg
A bot broadcasts every action made on your repo hosted on GitHub on the fedmsg message bus.
It is a web application that monitors GitHub repositories you subscribe it to. When new actions (commits, pull-request, tickets) are made, it broadcasts a message on the fedmsg message bus.
It is written in Python on the Pyramid framework, and uses velruse to talk with GitHub. It adds a webhook callback back to itself on repositories you ask it to monitor. When one of those callbacks fire, github2fedmsg republishes the message it receives to the fedmsg bus.
Hacking
If you run into trouble with these instructions, feel free to open a ticket or get in touch with me directly.
Fork and clone the following two repositories:
Using virtualenvwrapper:
$ cd github2fedmsg $ mkvirtualenv github2fedmsg $ python setup.py develop $ pip install waitress
Go off and register your development application with GitHub. Save the oauth tokens and add the secret one to a new file you create called secret.ini. Use the example secret.ini.example file.
Create the database:
$ initialize_github2fedmsg_db development.ini
Now, start the webapp:
$ workon github2fedmsg $ pserve development.ini --reload
0.0
Initial version
Release files for github2fedmsg 0.3.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| github2fedmsg-0.3.6.tar.gz | 345.5 kB | Without provenance | Details |
Release files / github2fedmsg-0.3.6.tar.gz
| Download URL | github2fedmsg-0.3.6.tar.gz |
|---|---|
| Size | 345.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a3fcfd1f96e26a362da326e7e03946bb8d6ab3006b5e01d9a519bdfe892ce2ad
|
|
BLAKE2b-256 checksum How to use checksums |
aed7fed30fdf57ae1ace1ef40f3423afc9db954988a7d542df058ad6d872e288
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for github2fedmsg 0.3.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
