Skip to content

Conversation

@BlaineAtAffirm
Copy link

Added an --allow-dirty option. I find this useful for large projects in which I might want to bump multiple version files with different versions. It would seem excessive to commit multiple one line changes separately so I have used this option to get around that.

@peritus
Copy link
Owner

peritus commented Mar 11, 2014

Thanks for the contribution.

I eventually want to lift that restriction entirely, it is just there as a safety measure because I don't trust my own software.

I'm currently working on #37 which should address your requirement much better, could you head over there and check whether the proposal covers your usecase (or chip in what would be required to fit your usecase)? Thanks.

@peritus peritus closed this Mar 11, 2014
@peritus peritus reopened this Mar 15, 2014
@peritus peritus added the v0.4.2 label Mar 24, 2014
@BlaineAtAffirm
Copy link
Author

updated tests to pass locally.

@peritus
Copy link
Owner

peritus commented May 12, 2014

Closing in favor of #37

@peritus peritus closed this May 12, 2014
@peritus peritus removed the v0.4.2 label May 26, 2014
@peritus peritus reopened this May 30, 2014
@peritus peritus added the v0.5 label May 30, 2014
@peritus
Copy link
Owner

peritus commented Jun 16, 2014

I implemented this for the upcoming version 0.5 — which you can install by running

sudo pip install https://github.com/peritus/bumpversion/archive/master.zip#egg=bumpversion-dev

I'd appreciate any testing before the release. Please note the new configuration format (documented in the README)

@peritus peritus closed this Jun 16, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants