Milestoner is a command line interface for crafting Git repository tags (milestones) using semantic versions. Each milestone is a summary of all commits made since the last milestone. You can use Milestoner to inspect what is currently pending or create a new release via a single command. By having a tool, like Milestoner, you can automate releases in a consistent and reliable fashion. Milestoner pairs well with the following gems:
Uses Versionaire for Semantic Versioning.
Ensures Git commits since last tag (or initialization of repository) are included.
Ensures Git commit messages are grouped by prefix, in order defined. For more details, see Git Lint Commit Subject Prefix for details. Defaults (can be customized):
Ensures Git commit messages are alphabetically sorted.
Ensures duplicate Git commit messages are removed (if any).
To install, run:
gem install milestoner
Command Line Interface (CLI)
From the command line, type:
USAGE: -c, --config ACTION Manage gem configuration. Actions: edit || view. -h, --help Show this message. -P, --publish VERSION Tag and push milestone to remote repository. -s, --status Show project status. -v, --version Show gem version.
milestoner --config edit milestoner --config view milestoner --help milestoner --publish 0.1.0 milestoner --status milestoner --version
This gem can be configured via a global configuration:
It can also be configured via XDG environment variables.
The default configuration is as follows:
:documentation: :format: "adoc" :prefixes: - Fixed - Added - Updated - Removed - Refactored
Feel free to take this default configuration, modify, and save as your own custom
configuration.yml file can be configured as follows:
Documentation Format (i.e.
documentation): Determines what format the release notes should be rendered as. This effects both status information from the command line and the release notes embedded within the body of a Git tag. Defaults to ASCII Doc (i.e.
adoc) but Markdown (i.e.
md) is supported too.
Git Commit Prefixes (i.e.
prefixes): Should the default prefixes not be desired, you can define Git commit prefixes that match your style. NOTE: Prefix order is important with the first prefix defined taking precedence over the second and so forth. Special characters are allowed for prefixes but should be enclosed in quotes. To disable prefix usage completely, use an empty array. Example:
To securely sign your Git tags, install and configure GPG:
brew install gpg gpg --gen-key
When creating your GPG key, choose these settings:
Key kind: RSA and RSA (default)
Key size: 4096
Key validity: 0
To obtain your key, run the following and take the part after the forward slash:
gpg --list-keys | grep pub
Add your key to your global (or local) Git configuration and ensure GPG signing for your tag is enabled. Example:
[tag] gpgSign = true [user] signingkey = <your GPG key>
Now, when publishing a new milestone (i.e.
milestoner --publish <version>), the signing of your
Git tag will happen automatically. You will be prompted for the GPG Passphrase each time unless you
are running the
Agent in the background (highly recommend).
To contribute, run:
git clone https://github.com/bkuhlmann/milestoner cd milestoner bin/setup
You can also use the IRB console for direct access to all objects:
To test, run:
bundle exec spec
Built with Gemsmith.
Engineered by Brooke Kuhlmann.