Milestoner

A tool for automating and releasing Git repository milestones.

Table of Contents

• Features
• Requirements
• Setup
• Usage
  • Command Line Interface (CLI)
  • Customization
• Tests
• Versioning
• Code of Conduct
• Contributions
• License
• History
• Credits

Features

• Ensures Semantic Versioning of Git repository tags:
  • Format: v<major>.<minor>.</maintenance>.
  • Example: v0.1.0.
• Ensures Git commits since last tag (or since initialization of repository if no tags exist) are included within each Git tag message.
• Ensures Git commit messages are grouped by prefix, in order defined, for each Git tag message (prefixes can be customized): "Fixed", "Added", "Updated", "Removed", "Refactored".
• Ensures Git commit messages are alphabetically sorted within each Git tag message.
• Ensures duplicate Git commit messages are removed (if any) within each Git tag message.
• Ensures Git commit messages are sanitized by removing extra spaces and [ci skip] text within each Git tag message.
• Provides optional security for signing Git tags with GnuPG signing key.

Requirements

1. A UNIX-based system.
2. MRI 2.x.x.
3. GnuPG.

Setup

For a secure install, type the following (recommended):

gem cert --add <(curl -Ls https://www.alchemists.io/gem-public.pem)
gem install milestoner --trust-policy MediumSecurity

NOTE: A HighSecurity trust policy would be best but MediumSecurity enables signed gem verification while allowing the installation of unsigned dependencies since they are beyond the scope of this gem.

For an insecure install, type the following (not recommended):

gem install milestoner

Usage

Command Line Interface (CLI)

From the command line, type: milestoner help

milestoner -P, [--publish=PUBLISH]  # Tag and push milestone to remote repository.
milestoner -c, [--commits]          # Show commits for next milestone.
milestoner -e, [--edit]             # Edit Milestoner settings in default editor.
milestoner -h, [--help=HELP]        # Show this message or get help for a command.
milestoner -p, [--push]             # Push local tag to remote repository.
milestoner -t, [--tag=TAG]          # Tag local repository with new version.
milestoner -v, [--version]          # Show Milestoner version.

For tag options, type: milestoner help tag

-s, [--sign], [--no-sign]  # Sign tag with GPG key.

For publish options, type: milestoner help publish

-s, [--sign], [--no-sign]  # Sign tag with GPG key.

When using Milestoner, the --publish command is intended to be the only command necessary for publishing a new release as it handles all of the steps necessary for tagging and pushing a new release. Should individual steps be needed, then the --tag and --push options are available.

Customization

Should the default settings not be desired, customization is allowed via the .milestonerrc file. The .milestonerrc can be created at a global and/or local level. Example:

• Global: ~/.milestonerrc
• Local: <project repository root>/.milestonerrc

Order of precedence for any setting is resolved as follows (with the first taking top priority):

1. CLI option. Example: A version passed to either the --tag or --publish commands.
2. Local project repository .milestonerrc.
3. Global ~/.milestonerrc.

Any setting provided to the CLI during runtime would trump a local/global setting and a local setting would trump a global setting. The global setting is the weakest of all but great for situations where custom settings should be applied to all projects. It is important to note that local settings completely trump any global settings -- there is no inheritance when local and global settings exist at the same time.

The .milestonerrc uses the following default settings:

---
:version: ""
:git_commit_prefixes:
  - Fixed
  - Added
  - Updated
  - Removed
  - Refactored
:git_tag_sign: false

Each .milestonerrc setting can be configured as follows:

• version: By default it is left blank so you'll be prompted by the CLI. However, it can be nice to bump this version prior to each release and have the current version checked into source code at a per project level. The version, if set, will be used to tag the repository. If the version is a duplicate, an error will be thrown. When supplying a version, use this format: <major>.<minor>.</maintenance>. Example: 0.1.0.
• git_commit_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 if used. To disable prefix usage completely, use an empty array. Example: :git_commit_prefixes: [].
• git_tag_sign: Defaults to false but can be enabled by setting to true. When enabled, a Git tag will require GPG signing for enhanced security and include a signed signature as part of the Git tag. This is useful for public milestones where the author of a milestone can be verified to ensure milestone integrity/security.

Tests

To test, run:

bundle exec spec

Versioning

Read Semantic Versioning for details. Briefly, it means:

• Patch (x.y.Z) - Incremented for small, backwards compatible bug fixes.
• Minor (x.Y.z) - Incremented for new, backwards compatible public API enhancements and/or bug fixes.
• Major (X.y.z) - Incremented for any backwards incompatible public API changes.

Code of Conduct

Please note that this project is released with a CODE OF CONDUCT. By participating in this project you agree to abide by its terms.

Contributions

Read CONTRIBUTING for details.

License

Copyright (c) 2015 Alchemists. Read the LICENSE for details.

History

Read the CHANGELOG for details. Built with Gemsmith.

Credits

Developed by Brooke Kuhlmann at Alchemists.