Replies: 2 comments
-
@coordt i saw on another post that you don't get notifications for new posts. My apologies if I am out of step tagging you here and this is not meant as a "please answer. me right now" more just a "hey, fyi, this is here when/if you have an opportunity to take a look". And thanks for this great tool. |
Beta Was this translation helpful? Give feedback.
-
First off, thanks for the support. I appreciate it! I'm unsure if I can give you a specific solution because I don't truly understand your desired workflow. But I will give you some guidance that might help. Two things to remember: the actual version always includes all the segments, and a segment typically depends on the previous segment. How does the For example, does version
After looking at this, you might be able to get what you want by splitting the I will warn you that you may regret a complex versioning convention. It means you will have to put more effort into managing it. Let me know if I helped at all. |
Beta Was this translation helpful? Give feedback.
-
First, this tool is awesome and I hope to use it to replace bash script i wrote a long time ago.
What I am trying to do is having a worklow that looks like:
main
|- v0.1.0
|- v0.2.0-rc0
|- v0.2.0-rc1
create PR #32 from branch feature/foo
feature/foo (pr #42)
|- v0.2.0-pr42.0
|- v0.2.0-pr42.1
|- v0.2.0-pr42.2
merge pr #42
main
|- v0.1.0
|- v0.2.0-rc0
|- v0.2.0-rc1
|- v0.2.0-rc2
release main
main
|- v0.1.0
|- v0.2.0-rc0
|- v0.2.0-rc1
|- v0.2.0-rc2
|- v0.2.0
I can't figure out the right way to do the parse and serialize to get this behavor. I can get the main branch rc behavor using the example from the docs. I have tried using a modified version of https://github.com/callowayproject/bump-my-version/blob/master/tests/fixtures/pep440.toml to do the pr tagging but with no luck.
Anyone do anythuing like this?
Beta Was this translation helpful? Give feedback.
All reactions