A changelog generator using simply structured git commit messages.
Project description
whathappened
A changelog generator using simply structured git commit messages
Inspired by
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 envrionment 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:
-o, --output PATH The changelog destination [default: stdout]
-e, --emoji Include emoji in headings if present
--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
Package Changelog
Created by Whathappened itself - very meta.
For the complete changelog, please see CHANGELOG.md.
Whathappened Commit Message Format
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
<scope>
is recommended to be a module, file, or folder name as appropiate.
For a nice summary of type
s and what they mean, please see Understanding Semantic Commit Messages Using Git and Angular.
Examples
All of the examples below are acceptable commit message formats:
The simplest message:
style: isn't it neat
Defining scope:
docs(gadgets): remember the gizmos
Signalling a breaking change
breaking feat: add the whozits
Defining scope, including a space:
fix (whatsits): repair the thingamabobs
Multiple lines:
test: How many have I got?
I've got twenty
But who cares?
I want more
For more examples, please see whathappened's own commits.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
File details
Details for the file whathappened-0.3.0.tar.gz
.
File metadata
- Download URL: whathappened-0.3.0.tar.gz
- Upload date:
- Size: 10.0 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.0.0 requests-toolbelt/0.9.1 tqdm/4.43.0 CPython/3.6.9
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 19426eab800001f7ade09a0d77212708949f198ad954568b274d0f29ce2faca7 |
|
MD5 | a735db0ff0ee9b25a215d9de8493124c |
|
BLAKE2b-256 | 3a26f837a532824271b92bd46daa7e8be598e3af7a805ce68b1dc8fd9296b733 |
File details
Details for the file whathappened-0.3.0-py3-none-any.whl
.
File metadata
- Download URL: whathappened-0.3.0-py3-none-any.whl
- Upload date:
- Size: 24.6 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.0.0 requests-toolbelt/0.9.1 tqdm/4.43.0 CPython/3.6.9
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | b0831e2adac9954e2e71d05fdc37c4d7dcc504fb6abb279b084d2a53e7d64770 |
|
MD5 | 38090fae7e35a70e6df61b78f77ff798 |
|
BLAKE2b-256 | ed2cfa670e0db4068c9f6e6ddd1618d2f091798b362fbcedc16d0a06a8917043 |