NAME

repomatic squashed-release - Report a release pull request merged by squashing

SYNOPSIS

repomatic squashed-release [OPTIONS]

DESCRIPTION

Open an issue when a release pull request was squash-merged, then fail.

A release needs its freeze and unfreeze commits to land separately, through "Rebase and merge". Squashing them leaves no release commit to tag, so no tag, package or GitHub release is published. This reports that to the maintainer in one issue, rendered from the squashed-release template and assigned to the workflow actor, and exits with code 1.

A re-run updates the open issue instead of opening a second one, and a later squash merge reopens it.

Exits with code 0, opening nothing, when the message is not the one of a squash-merged release pull request.

OPTIONS

--message TEXT: Commit message to check. Defaults to the head commit message of the event in $GITHUB_EVENT_PATH.
--repo TEXT: Repository to open the issue in. Defaults to $GITHUB_REPOSITORY, then to the GitHub remote of the current clone.
--help / -h: Show this message and exit.

ENVIRONMENT

SQUASHED_RELEASE_COMMIT_MESSAGE: Commit message to check. Defaults to the head commit message of the event in $GITHUB_EVENT_PATH.
GITHUB_REPOSITORY: Repository to open the issue in. Defaults to $GITHUB_REPOSITORY, then to the GitHub remote of the current clone.
SQUASHED_RELEASE_REPO: Repository to open the issue in. Defaults to $GITHUB_REPOSITORY, then to the GitHub remote of the current clone.
SQUASHED_RELEASE__CLICK_DEFAULT_HELP: Show this message and exit.

EXIT STATUS

0: Success.
1: A runtime error, an aborted prompt (Ctrl-D), or a declined confirmation.
2: A usage error: unknown option, invalid value, missing operand, or an unparsable configuration file.
130: Interrupted with Ctrl-C: the process ends by SIGINT, reported as 130.

EXAMPLES

Check the head commit of the current push event

repomatic squashed\-release

Check an explicit commit message

repomatic squashed\-release \-\-message 'Release `v1.2.3` (#42)'

AUTHORS

Kevin Deldycke