bboughton/Release

Create releases when Pull Requests are merged.

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Stalelast commit Oct 26, 2024
License: None

Pinned Snippet

workflow.ymlSHA-pinned

uses: bboughton/release-action@f3aa6443f622ef6e234a73e9582ee3cfcceed5c4 # v0.1.0

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
token	Personal access token (PAT) used to access the repository.	—	${{ github.token }}
pr_number	Pull Request associated with run.	—	${{ github.event.number }}
monorepo	Set to true when multiple releases are needed. This is useful in a mono-repository where multiple artifacts are produced and released independently. Release versions and git tags will have a namespace prefix in order to clearly identify which module or subcomponent the release is associated with. For example if the release is related to the 'foo' component the release would be 'foo/v0.1.0'. The name of the module will be determined using labels on the pull-request. See 'namespace_label_prefix' for more details.	—	false
module_label_prefix	Configure the prefix of the label used to identify which module(s) a pull-request is associated with. During the release process labels that begin with this value will be retrieved from the pull-request and for each one a release will be created. The release version will be prepended with the module name minus the namespace prefix. For example if a pull-request contains the label 'module/a' than the release be 'a/v0.1.0'.	—	module/

Outputs

name	description
tag	Release tag