whathappened
A changelog generator using simply structured git commit messages
Inspired by
and
Install and Run
Installation is as simple as it gets:
$ pip install whathappened
To generate a changelog, run:
$ whathappened
Make sure to activate any virtual environment that you might be using first.
Some options are available:
$ whathappened --help
Usage: whathappened [OPTIONS] [GIT_LOG_ARGS]...
Handle command line arguments. Extra arguments are passed to 'git log'.
Options:
--overriding-version TEXT Specify a version number to use [format: x.y.z]
-o, --output PATH The changelog destination [default: stdout]
-e, --emoji Include emoji in headings if present
-d, --development Include development-related commits
-p, --prefix TEXT Version prefix, often 'version' or 'v' [default: '']
--version Show the version and exit.
--help Show this message and exit.
To limit the range of commits, add a revision range argument.
To create a changelog of commits that are yet to be pushed:
$ whathappened origin..HEAD
To create a changelog of commits between (branch: main) and (tag: v1.0.0) and write the output to file:
$ whathappened -o CHANGELOG.md main..v1.0.0
To create a development changelog, with addition headings like 'Testing' and 'Reverted':
$ whathappened -d
Package Changelog
Created by Whathappened itself - very meta.
For the complete changelog, please see CHANGELOG.md.
Whathappened Commit Message Format
For a full description of the message format, see Commit-It-Simple.
Whathappened expects git commit messages in the format outlined below:
[optional breaking ]<type>[ optional (<scope>)]: <description>
[optional body]
<type> is recommended to be one of:
fix
feat
build
ci
docs
style
refactor
perf
test
Variations on these types like feat, feature, features, or doc, docs are seamlessly grouped together.
The <scope> is recommended to be a module, file, or folder name as appropriate.
More examples can be viewed on whathappened's own commits.
For a nice summary of types and what they mean, please see Understanding Semantic Commit Messages Using Git and Angular.
Emoji
Adding the --emoji flag will add emoji after each heading in the changelog. Below are the emoji that are used:
Production:
- Docs 📝
- Features ✨
- Fixes 🐛
- Performance ⚡️
- Refactorings ♻️
- Other 🃏
Development:
- Continuous Integration 🤖
- Reverted ☠️
- Testing 🧪
Metadata
Release files for whathappened 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| whathappened-1.1.0.tar.gz | 12.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| whathappened-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.6 kB
Release files / whathappened-1.1.0.tar.gz
| Download URL | whathappened-1.1.0.tar.gz |
|---|---|
| Size | 12.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f3ac2129cd92aca74f17980bcd87c06b50375f20a2b0c8d124ec4dba14c4a1e6
|
|
BLAKE2b-256 checksum How to use checksums |
8b6c04103f8547d51dc6736a5d72b7a5c844092702dc534171eb3d9153330bfa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.22.0 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.8.5
|
Release files / whathappened-1.1.0-py3-none-any.whl
| Download URL | whathappened-1.1.0-py3-none-any.whl |
|---|---|
| Size | 24.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ad6a8a834366598758e9bb8c58bbf4f86d8c5966972cb2e8de234304be03a576
|
|
BLAKE2b-256 checksum How to use checksums |
6b870451021827bee55176d67b819254187c4a04c03cde5060df7b8a6b85f543
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.22.0 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.8.5
|