-
Notifications
You must be signed in to change notification settings - Fork 23
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
Log.txt file automatic creation in PWD is kind of an anti-feature #165
Comments
Second option is good 👍 PR welcome 🙏 |
Also, is the log file supposed to output things? I just ran the tool and updated my code (44 lines changed) and there was nothing in the log file. edit: looking into it, seems like it only outputs when an error occurs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, great tool, but I have a bit of a UX nitpick. By default, every time you run
bump-pydantic
it generateslog.txt
in the current directory. This is usually at the project root of a repo and I really don't care about the log file 99% of the time, and I have to remember not to accidentally git commit it. I would add a rule but for a basically one-off process it seems unnecessary.I think it would be a better experience if it did one of the following:
--log-file
option is requested/tmp/bump-pydantic/log.txt
)--no-log-file
to suppress the generation of the log file. (I suppose I can--log-file=/dev/null
but I have to remember that each time)The text was updated successfully, but these errors were encountered: