Ask HN: What's the one feature you'd want in a GitHub productivity tool?
I’m building a tool that analyzes your GitHub activity to boost productivity.
Before I start developing, I’d love to hear from the community:
What’s the one feature you’d want most in a GitHub productivity tool?
Drop your ideas below, and I’d really appreciate your feedback to help shape the tool!
48 comments
[ 2.5 ms ] story [ 98.4 ms ] threadIt works great for eliminating the «what did I actually work on X days ago?» problem (that used to be the bane of my existence)
Disclaimer: I work at Timely
I’m looking for ‘a tool’ like this to help manage code changes and communicating about those releases across a set of github repos.
it'd make my life easier to know who let the bug into prod
But… that’s probably not in scope for your tool.
I want the PR's to be so good and well tested that I can actually approve them and commit them to the project.
1) Click on a file 2) Click blame 3) Click the parent commit SHA 4) Click View File 5) Click blame
Repeat as you traverse back in history.
git log -L 40,50:app/models/user.rb
This page provides some other techniques: https://tekin.co.uk/2020/11/patterns-for-searching-git-revis... but I think they have their own limitations.
Everytime I refresh the page on a large PR I have to click through 10-12 "Load more" buttons before I can have the whole picture.
https://docs.github.com/en/communities/documenting-your-proj...
- Main view is not the code, nor can I approve from that view, so it’s always half a dozen clicks to review even something trivial. - The main conversation view is very broken for me. Conversations always get lost or forgotten. - Any long conversation gets hidden behind another button and trying to load or find something at that point is very hard - There is a concept of resolving threads but no way to see if there are any unresolved threads
I am probably missing some but these are the largest issues for me
Tools like Graphite, CodePeer, Codelantis (and of course CodeApprove) make it so much easier to have a meaningful discussion on a PR. Making sure every thread comes to resolution, knowing whose turn it is, having a fast way to navigate between code and comments, etc. The FAANG companies all have this kind of thing built in house because good code review is a key part of building high quality large software projects.