search

hinnefe2 / gitrisky

Predict code bug risk with git metadata
MIT License
42 stars 15 forks source link

Add verbose option to generate more logging #9

Open hinnefe2 opened 6 years ago

hinnefe2 commented 6 years ago

For larger commit histories it would be nice to have more detailed logging about the steps in model training (e.g. 'building features', 'calculating labels', 'training model'). We should probably be using the logging module anyway. Or maybe tqdm progress bars?

nm17 commented 6 years ago

@hinnefe2 I would like to help out!

hinnefe2 commented 6 years ago

Awesome! This issue is a great place to start.

If you haven't already, checkout CONTRIBUTING.md for the recommended workflow (basically fork, make a branch, add your code to the branch, then open a pull request).

For this issue I was thinking we should add some logging (with python's standard library logging module) to cli.py to track the different steps. We could also add another option to the command line tool to turn the logging on or off (maybe by setting the logging level).

If this sounds good to you then this issue is all yours!