Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allowing projectId to accept a regular expression to create releases spanning multiple boards #57

Open
raygpt opened this issue May 11, 2021 · 1 comment

Comments

@raygpt
Copy link

raygpt commented May 11, 2021

We have a project that has ticket numbers belonging to multiple project boards. How difficult would it be to allow projectId to be a regular expression so that this plugin can create releases spanning multiple boards?

@ab-arao
Copy link

ab-arao commented May 27, 2021

I think we'd like to have the same feature but am not sure from the description of your question.

If you are saying the following:

We have a [Github repo] that has ticket numbers belonging to multiple project[s]. How difficult would it be to allow projectId to be a regular expression so that this plugin can create releases spanning multiple boards?

Then I think we'd also like this feature request.

I think this could be accomplished with the following configuration:

{
	"plugins": [
		"@semantic-release/commit-analyzer",
		"@semantic-release/release-notes-generator",
		"@semantic-release/git",
		[
			"semantic-release-jira-releases",
			{
				"jiraHost": "uphabit.atlassian.net"
			},
			{
				"projectId": "UH",
				"releaseNameTemplate": "Test v${version}",
				"ticketPrefixes": ["TEST", "UH"],
				"ticketRegex": "[a-zA-Z]{3,5}-\\d{3,5}"
			},
			{
				"projectId": "project-2",
				"releaseNameTemplate": "Project 2 v${version}",
				"ticketPrefixes": ["TEST2", "UH2"],
				"ticketRegex": "[a-zA-Z]{3,5}-\\d{3,5}"
			}
		]
	]
}

This would require changing the signature of PluginConfig and also iterating through each new project/ticket config but otherwise the plugin would stay the same.

I'd be very happy to take a crack at this if the PR for #58 would get merged in!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants