pull down to refresh
Thank you for asking my question
@sorukumar you'll want to use --no-merges
Thanks for pointing that out. In the new report I do pull everything, but I treat merge commits separately—check the Total/Author toggle in the Contributor Galaxy charts.
https://sorukumar.github.io/orange-dev-tracker/contributors.html
Any numbers look off to you?
Appreciate you taking the time to comment
No. it would be a good next step.
Additionally, i am debating whether it make sense to break commits into components like wallet, consensus, networking, GUI and others. it would add insights on the kind of work that is being done. What could those components be? and, then I need to figure out a way to group it from the commit log.
A lot of coding around testing... in python, which is interesting choice given the code base is C++
Is this always the case for large C++ projects?
No, that would certainly not always be the case. In this case, it’s used for the tests that treat Bitcoin Core as a black box, especially the functional tests, and benchmarks that call RPC commands of the binary and expect specific outcomes. It’s just simpler to use a scripting language for these tests.
gotcha
deleted by author
Did you distinguish merge commits from other commits?