Contents
Overview
dbrownell_CommitEmojis offers command line tools useful when creating git commit messages based on gitmoji.
How to use dbrownell_CommitEmojis
Display
| Scenario | Command |
|---|---|
| Without installation | uvx --from dbrownell_CommitEmojis commit_emojis Display |
| When installed as a package dependency | uv run commit_emojis Display |
Transform
| Scenario | Command |
|---|---|
| Without installation | uvx --from dbrownell_CommitEmojis commit_emojis Transform <commit message> |
| When installed as a package dependency | uv run commit_emojis Transform <commit message> |
Examples for <commit message> are:
| Input | Output |
|---|---|
| :+project: Initial checkin | 🎉 [+project] Initial checkin |
| :+feature: A new feature was added | ✨ [+feature] A new feature was added |
See Display for a list of all supported emoji and alias values.
Installation
| Installation Method | Command |
|---|---|
| Via uv | uv add dbrownell_CommitEmojis |
| Via pip | pip install dbrownell_CommitEmojis |
Verifying Signed Artifacts
Artifacts are signed and verified using py-minisign and the public key in the file ./minisign_key.pub.
To verify that an artifact is valid, visit the latest release and download the .minisign signature file that corresponds to the artifact, then run the following command, replacing <filename> with the name of the artifact to be verified:
uv run --with py-minisign python -c "import minisign; minisign.PublicKey.from_file('minisign_key.pub').verify_file('<filename>'); print('The file has been verified.')"
Development
Please visit Contributing and Development for information on contributing to this project.
Additional Information
Additional information can be found at these locations.
| Title | Document | Description |
|---|---|---|
| Code of Conduct | CODE_OF_CONDUCT.md | Information about the norms, rules, and responsibilities we adhere to when participating in this open source community. |
| Contributing | CONTRIBUTING.md | Information about contributing to this project. |
| Development | DEVELOPMENT.md | Information about development activities involved in making changes to this project. |
| Governance | GOVERNANCE.md | Information about how this project is governed. |
| Maintainers | MAINTAINERS.md | Information about individuals who maintain this project. |
| Security | SECURITY.md | Information about how to privately report security issues associated with this project. |
License
dbrownell_CommitEmojis is licensed under the MIT license.
Metadata
Release files for dbrownell-CommitEmojis 0.5.3
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 | |
|---|---|---|---|---|
| dbrownell_commitemojis-0.5.3.tar.gz | 14.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dbrownell_commitemojis-0.5.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.7 kB
Release files / dbrownell_commitemojis-0.5.3.tar.gz
| Download URL | dbrownell_commitemojis-0.5.3.tar.gz |
|---|---|
| Size | 14.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
29f3b273f433da0f6605e73f92ed525b5d9658ed5f0babded1a2bd5950eccb57
|
|
BLAKE2b-256 checksum How to use checksums |
0ea29b798ffec05aad2420d0902b8749c6b572e6eab64f928c5a63f98a1d5192
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / dbrownell_commitemojis-0.5.3-py3-none-any.whl
| Download URL | dbrownell_commitemojis-0.5.3-py3-none-any.whl |
|---|---|
| Size | 16.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c5ce23f1e6d0703fda0f0fd294f2d0c5172fc00e086a63f36904114bb7f14bfc
|
|
BLAKE2b-256 checksum How to use checksums |
5c3276a10736a211e578c6e38d8b98385d067c01f98a4c396dd8efe4a67e164a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for dbrownell-CommitEmojis 0.5.3
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.