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

Can I configure the pattern of release tags? #1497

Closed
mrchrmn opened this issue Jun 30, 2022 · 2 comments
Closed

Can I configure the pattern of release tags? #1497

mrchrmn opened this issue Jun 30, 2022 · 2 comments
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue.

Comments

@mrchrmn
Copy link

mrchrmn commented Jun 30, 2022

Is it possible to change the naming pattern of the tags generated by each release? I would prefer the tag to start with the version number in order for it to be recognised as a semantic version in our pipeline.

Unfortunately I haven't found a way to configure it through the settings file. In the code I see there are options for "v or no v" and the separator but that seems to be it.

We use the release-please Github Action, by the way, not the CLI.

Thanks for reading this :)

@mrchrmn mrchrmn added priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue. labels Jun 30, 2022
@chingor13
Copy link
Contributor

Are you looking for just the version number? Or an actual different pattern (e.g. 1.2.3 component-name)?

For skipping a component name, there should be an include-component-in-tag manifest option.

@mrchrmn
Copy link
Author

mrchrmn commented Jul 1, 2022

Thanks for the quick reply. This might actually be enough.

I was not aware of this option, because it is not mentioned in this document, from which I cobbled together my configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue.
Projects
None yet
Development

No branches or pull requests

2 participants