-
Notifications
You must be signed in to change notification settings - Fork 7
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
Connect #28 historical analysis #29
Conversation
d43ec4c
to
dce8aa5
Compare
dce8aa5
to
78dad5f
Compare
@seanmarcia since you were interested in/suggested the debt clock idea (#2) hopefully this will be of some interest to you... it needs refactoring, cleanup and tests (I think I want to use open3/popen3 instead of simply shelling out to git, as the warnings when failing to show git notes get noisy), but this is a surprisingly usable v1... it should only take a long time to run once, then be fairly fast afterwards, and can hook into the output data structure from |
c4503ac
to
c573de4
Compare
Using Open3 to avoiding noisy output to stderr etc Still some blank lines coming out, from where? Also logic changes to travel back to original branch rather than detached head state
057e5b0
to
f5866a3
Compare
Note to self/others: since the main usecase for this historical data might be on a CI server, it will git clone the repo everytime and blow away any git notes created.... so we should probably also support Redis, by checking if Redis gem is installed and some config present, and if so cache data there instead? |
@bglusman This is begging to be a SAAS product that would store the history, just like CodeClimate does. Have you given that any thought? |
6951f19
to
bef0b7f
Compare
Extract method for cleanup and raise debt limit because I exceeded current ceiling, sigh
bef0b7f
to
6300d99
Compare
Add
archeological_dig
clas andDebtCeiling.dig
feature for historical debt analysis.