-
-
Notifications
You must be signed in to change notification settings - Fork 180
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
Is it possible for releases branches always have the same name? #5
Comments
Currently it can't be configured. |
@elmart Any progress? Do you still need this? |
Sorry, I didn't find the time to investigate more. Closing this by now. I'll reopen if/when I make advance on this. Thanks. |
@elmart After few changes it became rather trivial to implement this. Could you clone, build/install and test with |
|
I see that it's possible to configure branch names/prefixes.
But it seems implied that, particularly, release branches will always be of the form
prefix + version
.At my day job, release branch is always called the same way, with no version info. It gets created when starting a new release and deleted after that. There are never two releases in parallel, so that poses no problems.
So, can this plugin be configured somehow to achieve that workflow, and have release branch always being named the same?
If not, could you point me to the place in code where I should patch to achieve it?
I can explore code and find out on my own, but I'd be grateful if you saved me that time.
I would issue a PR with my patch in that case.
Thanks.
The text was updated successfully, but these errors were encountered: