Create releases in GitHub using release notes from a Jira version.
npm install -g greleaser
export JIRA_ORGNAME='myjiraorg' export JIRA_USERNAMEfirstname.lastname@example.org' export JIRA_PASSWORD='jirapassowrd' export GITHUB_USERNAME='me' export GITHUB_PASSWORD='githubpassword' export GITHUB_ORG_NAME='mygithuborg'
Note that if you use 2FA on GitHub, you'll need to use a personal access with the
repo scope in place of your GitHub password.
greleaser -p <projectId> -v <versionNumber> -g <gitHubRepo>to create a release in GitHub using the release notes from Jira.
You specify the GitHub project name on the command line with the
By default, the
master branch is tagged, but you can choose a different commit with the
-c command line argument.
The tag name will be the version number pulled from the Jira version name. For example, if your Jira version is named
v1.0, then the GitHub tag will be named
v1.0. You can override the tag name with the
You can name your Jira releases however you like, but Releaser is going to split the name on a space and use the last result in that array.
v1.0 in Jira becomes
v1.0 in GitHub
API v1.0 becomes
v1.0 in GitHub
v1.0 API becaomse
API in GitHub
If this doesn't suit you, you can pass different release and tag names with the
-t options respectively.
Release notes are not available in the Jira Cloud REST API.
greleaser -p 10003 -v 10001 -g my-github-project
v1.0in project 10003 to
my-github-project, tag commit
dca12345, tag the commit as
version1and call the release
greleaser -p 10003 -v 10001 -g my-github-project -c dca12345 -t version1 -r "My Release"