Brainstorm: Querying

[advdv]

Having intimate knowledge of both code commits and the time it took to create them opens up enormous potential for interesting data to be extracted. What would you like to query?

[rebelzach]

Being able to query by date or a certain number of days in the past. (i.e. See the total effort for the last 7 days)

[rebelzach]

To start with: just passing a commit hash and receiving the total effort (for each contributor) since that commit would be great.

[advdv]

@rebelzach , thanks for the input - these are indeed the most obvious cases, if I may ask: how would you use such data in your everyday work, solely for you own or maybe in code reviews? I'm interested to learn how a tool like Timeglass (and its data) can provide value to the whole team.

[rebelzach]

At work we are more concerned with having a true measure of time effort per feature. So being able to query and see the effort for a particular merge from a feature branch would be really awesome.

[advdv]

@rebelzach I've just drafted a new release that includes a mechanism for querying your data: https://github.com/timeglass/glass/releases/tag/v0.5.1
A guide to using it can be found here, let me know what you think!

[rebelzach]

At a glance, this seems to be working. I really like the use of piping the git output into glass, that makes it so flexible! Great work, I'm pretty sure this tool is changing my life. 🎉