You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We operate in a monorepo with a tag naming convention like packagename-v1.2.3. Currently, to support this, we need each project to specify a pattern in their [tool.poetry-dynamic-versioning] section, and this is a little finicky (it's a long, scary regex that we have a make a copy of for each project in our monorepo).
Would you be open to a generic setting for this? I'm thinking something like an optional pattern-prefix option that we could set to "packagename-", and then we wouldn't have to set pattern at all.
I'd be happy to send in a PR for this if you're open to it. That said, I also completely understand if this is not a feature you want to support (as I mentioned before, the existing pattern option does work for us, it's just a little finicky).
The text was updated successfully, but these errors were encountered:
First off, thanks for the great tool!
We operate in a monorepo with a tag naming convention like
packagename-v1.2.3
. Currently, to support this, we need each project to specify apattern
in their[tool.poetry-dynamic-versioning]
section, and this is a little finicky (it's a long, scary regex that we have a make a copy of for each project in our monorepo).Would you be open to a generic setting for this? I'm thinking something like an optional
pattern-prefix
option that we could set to"packagename-"
, and then we wouldn't have to setpattern
at all.I'd be happy to send in a PR for this if you're open to it. That said, I also completely understand if this is not a feature you want to support (as I mentioned before, the existing
pattern
option does work for us, it's just a little finicky).The text was updated successfully, but these errors were encountered: