.bumpversion.cfg's current_version gets removed about bumpversion HOT 4 CLOSED

If you're also using git tags, subsequent runs will use these to get the latest version. However, you're not the first one confused by this, so I should probably remove this "feature".

Thank you for this bug report.

Sent from my pocket calculator

Am 26.09.2013 um 22:04 schrieb Grzegorz Śliwiński [email protected]:

I defined current_versionin bumpversion.cfg file, but after I bumped version, it got removed from the file completely. Shouldn't it be just updated?

—
Reply to this email directly or view it on GitHub.

from bumpversion.

I use both auto commit, and auto tag feature :) Well... used twice actually, just started yesterday.

But isn't removing this line altogether from .bumpversion.cfg during bumping process counter productive? To use bumpversion again, you have to add this line back, and commit the file, because bumpversion can't work on dirty tree either ;)

from bumpversion.

No, at the moment you should be able to just bump the version again. bumpversion uses 'git describe' to find the current_version independent of the config file.

Sent from my pocket calculator

Am 27.09.2013 um 19:21 schrieb Grzegorz Śliwiński [email protected]:

I use both auto commit, and auto tag feature :) Well... used twice actually, just started yesterday.

But isn't removing this line altogether from .bumpversion.cfg during bumping process counter productive? To use bumpversion again, you have to add this line back, and commit the file, because bumpversion can't work on dirty tree either ;)

—
Reply to this email directly or view it on GitHub.

from bumpversion.

hmmm... ahhhh... I know what I did wrong yesterday

from bumpversion.