-
Notifications
You must be signed in to change notification settings - Fork 129
Implementation of the independent feature from ADVbumpversion #234
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
Conversation
Thanks, would be great to 'merge user bases' with ADVbumpversion! |
As soon as the new version of bump2version is released, I will put the ADVbumpversion GitHub project in Archived state, and change the README to explain how to migrate to bump2version (since the syntax is a little bit different when using the same file in different rules). I will also probably shutdown the project on PyPi or make it clear that it is deprecated. Also, if you need help for bump2version, let me know. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good stuff, and it's great to consolidate projects!
Could you rebase on master?
Surely, the pull request backlog could use some love. Supporting Python 3.9 and 3.10 would be great! |
But it is already the case. |
Master branch has been updated in the meantime... "This branch is 3 commits ahead, 4 commits behind c4urself:master. " |
Any plan to make a new release and update the Pypi version? I am waiting for this in order to kill my fork and redirect people to this project. |
This is an implementation (back port) of the
independent
feature from ADVbumpversion, as discussed in #121. This feature implements #81. If this PR can be merged, I will close ADVbumpversion fork and redirect people to bump2version.