seems to be the exact same as #141, just with release create.
berg release create fails with values provided by flags #249
Hey thanks for reporting this. I will try to fix this next and add a regression test!
I think this is actually coming from the fact that the command requires an existing tag atm. You probably don't have one and the error message is just bad.
I will see if I can implement a workflow that includes creating a tag if it is missing!
@Aviac wrote in #249 (comment):
I think this is actually coming from the fact that the command requires an existing tag atm. You probably don't have one and the error message is just bad.
I will see if I can implement a workflow that includes creating a tag if it is missing!
furthermore it seems that tags have to start with v which might also be the cause of the error. I'll make sure to make this feature more robust. It is very new still 😅
@tippfehlr Should be fixed in main now :) You still need to create tags manually at. Feel free to leave a feature request. I thought that it would be nice to fix this independently first and continue with writing more tests. UX improvements will be made in the future.
Thanks again for the issue creation! 💚
The tag was indeed missing because I just pushed it (seems like it needs a second).
Thanks a lot for the quick fix ❤️
Something is not working
Contributions are very welcome, get started here
No description
This issue or pull request already exists
Interested in contributing? Get started here.
Need some help
Something is wrong
More information is needed
No description
Related to an upstream repository, already reported there
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?