Because I want sound effects to go with my git commands… and I want them to work everywhere: a shell, a GUI, a Putty session.
Installing
$ pip install GitBansheeUsing
1. cd into any git repository
$ cd flask/2. type the git-banshee command
$ git-banshee
> Hooks have been installed, go to: http://205.186.163.125/?hash=yawubgzjlxlb
> Server running3. go to the url. Now whenever a ‘commit’, ‘merge’ or ‘checkout’ happen whilst the server is running, a sound effect will be played in the browser.
Todo and ideas
Daemon mode for server
Usable way to choose sounds
Pretty web page
More sounds
1 maintainer
Metadata
1 maintainer
Release files for GitBanshee 0.1
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 | |
|---|---|---|---|---|
| GitBanshee-0.1.tar.gz | 440.3 kB | Without provenance | Details |
Release files / GitBanshee-0.1.tar.gz
| Download URL | GitBanshee-0.1.tar.gz |
|---|---|
| Size | 440.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ce67195dd6e15edca0b0b81068af7fab827da38334be1f6b308960a10d629d28
|
|
BLAKE2b-256 checksum How to use checksums |
6c33c07d6723b25554a0ca01fb1bcb84611cdc4211cf1bd6079ed269a4b1139c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for GitBanshee 0.1
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.
