Propagate current_version and new_version to commit #70
Conversation
|
@ekohl do you have rights for bump2version in AppVeyor? I have been trying to figure out why the tests fail. The strangest thing is that for my bump2version fork I reran the tests for the latest commit in this repo (Jan 10, 2019), and surprisingly even though they were successful in this repo they were unsuccessful in my fork. I started a discussion with AppVeyor support (https://help.appveyor.com/discussions/problems/23659-python-tests-successful-in-jan2019-but-same-code-and-tests-fail-may2019). They ask if someone could trigger a rerun of the tests for the latest commit of this repo. Could you please do this? I tried contacting @c4urself but has been a while and haven't received any response. |
|
@mauvilsa -- i've run a rebuild but i've rebuilt some of my other commits as well and I think there's a deeper issue with tox/PYTHONPATH |
|
@c4urself I understand that with #73 the AppVeyor problem is solved. But some time has passed and that pull request hasn't been merged. Also it has been many months since there hasn't been a new release of bump2version that is made available in pypi. Is it likely that any time soon this pull request be merged and a released that includes it be available in pypi? |
|
@ekohl do you think this pull request has a chance to be approved and be included in the next release of bump2version? |
|
@mauvilsa yep, please rebase, I'll try to get this in next release. |
…riables so that pre-commit hooks can distinguish between normal commits and bumpversion commits.
- Added feature to README.md so that it is properly documented.
Propagate current_version and new_version to commit as environment variables so that pre-commit hooks can distinguish between normal commits and bumpversion commits.