nextdoor/Helm Create Tag from Version Action

Automates the process of pushing merge commits into a "release" branch from either a source branch (ie `main`) or from Git Tags/Releases.

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Stale
License: None

Inputs

name	description	required	default
dry	Whether or not this action will run in a dry run or not.	no	false
verbose	Should the script output all of the commands (set -x) while its running or not?	no	false
chart_dir	The path to where the chart lives (specifically the directory that holds the Chart.yaml file).	yes	chart
tag_user_name	The username that will the Git tag will be made on behalf of.	yes	${{ github.actor }}
tag_user_email	The email that will the Git tag will be made on behalf of.	yes	${{ github.actor }}@users.noreply.github.com
tag_message	A string applied to the Tag to help provide a record of who made the action, when, and why.	—	Automated Helm Release by ${{ github.actor }} from Commit SHA ${{ github.sha }} (Branch: ${{ github.head_ref }})
force	If true, then the git tag event (and the git push) will be forced. This will overwrite existing tags.	yes	true
release_tag	If supplied, this tag will be used as an "alias tag" that is continually updated and moved to point to the most recent Helm Chart release tag. Eg. If you have app-1.2.3 and you release app-1.2.4, the "alias tag" will be moved from app-1.2.3 to app 1.2.4. This is useful for maintaining a "stable" or "production" pointer tag for CI tooling for developers. Note: Make absolutely sure that if you have multiple charts in your repository that you customize this to include the chart name - otherwise this value will be moved around between charts.	no	—
create_release	Whether or not to also create a Github Release for this tag?	yes	true
release_message	The release message that is shown in the Github Releases UI for this release.	—	Automated Helm Release by ${{ github.actor }} from Commit SHA ${{ github.sha }} (Branch: ${{ github.head_ref }})

Outputs

no outputs