-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
current_version not bumped in config when on a network mapped drive #253
Comments
I understand what you are seeing and why it happens. bump-my-version does not change configuration files that it detects are outside the repo because some people host the configuration in a central place. It seems the method of detection should be improved. I don't have the ability to re-create your scenario to test out different methods. Can you offer some ideas to determine if the configuration is within the git repo? I'm obviously just doing some basic path checking. Is there a better way? |
From my previous experience with python-semantic-release I wonder if this is caused by the issue that Windows paths are represented a) in the classic way with a drive letter or b) as UNC Path. To translate classic to UNC Representation somewhere a .resolve() could be missing. |
I can confirm the error and the root cause. generate-changlog accesses the file via the Path with a drive letter. |
try to change line 131 in bumpversion/config/files.py |
I confirm this fixes the issue. |
Description
Trying to get done
bump-my-version bump minor
in a Git repository that is located on a network mapped drive in Windows 10. It does not matter if bumping major/minor/patch.What happened
.bumpversion.toml
), but thecurrent_version
was not bumped in.bumpversion.toml
.Finding the cause
bump-my-version bump minor -vvv
, one of the outputted lines showed"Configuration file is outside of the repo. Not going to change."
. That message stems from update_config_file(). It lead me to rungit rev-parse --show-toplevel
to check my Git repository's root directory, which pointed to a different path thanpwd
due to my Git repository being located on a network mapped drive.Workaround
The text was updated successfully, but these errors were encountered: