Code Review - an idea

Hello, you magnificent beasts who write the best code that works on the first try.

I am in a pickle now, since I do sometimes review the code of my colleagues at work OR they do review mine. So now I’d love to see where during this month did I put my comments and which branches did I review. We do have an option to see the files “checked” when reviewing, but is there a tool to see how long have we been doing that?

Why the question: the more of a senior you are you probably spend more time reviewing than writing the code (don’t quote me on that, it’s just a prediction :)) so if you’re going to ask someone to pay you it’d be nice to show what actual work did you do. Saying “I reviewed code” is too broad and brings confusion.

So my question is: how do you guys track that stuff? :slight_smile:

1 Like

Hi Lukortech! :wave: You’re right that there’s no kind of time tracking built natively into GitHub. (Perhaps you’d like to submit a feature request through our official product feedback form so that our product team know you’d find it useful?)

I used to work in Accountancy and Law firms where people had to track their time in 15 minute chunks (or stranger increments, sometimes!) so they knew exactly how much to charge their clients - there are a bunch of apps available to help you do that sort of thing:

I’d be interested to see what other methods people use to track their time doing code reviews or if there’s other ways that people “show their work” so to speak. Is time always tracked for external clients, or do some people use time tracking internally as well? :thinking: