I want an AI to take issues and turn them into PR's. I want the PR's to be so good and well tested that I can actually approve them and commit them to the project.
Ask HN: What's the one feature you'd want in a GitHub productivity tool?
21–30 of 49 posts
Re: Ask HN: What's the one feature you'd want in a GitHub productivity tool?
#22Re: Ask HN: What's the one feature you'd want in a GitHub productivity tool?
#231) 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.
Re: Ask HN: What's the one feature you'd want in a GitHub productivity tool?
#24Everytime 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.
Re: Ask HN: What's the one feature you'd want in a GitHub productivity tool?
#25Tell me all the commits I've made for the day across all repos. Can be very helpful when attempting to capture time logs. I often work across several projects and/or several branches in a project daily.
It 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
Re: Ask HN: What's the one feature you'd want in a GitHub productivity tool?
#26Re: Ask HN: What's the one feature you'd want in a GitHub productivity tool?
#27Re: Ask HN: What's the one feature you'd want in a GitHub productivity tool?
#28Something to view ALL pull requests that i need to review, across repos?
Re: Ask HN: What's the one feature you'd want in a GitHub productivity tool?
#29Re: Ask HN: What's the one feature you'd want in a GitHub productivity tool?
#30A chronological list of all the commits that affected a line of code. I've often gone and looked at a line, looked at the blame for that line, and then had to traverse backwards through history to find where the change I'm interested in happened. Using the GitHub UI, this takes a considerable amount of clicks. 1) Click on a file 2) Click blame 3) Click the parent commit SHA 4) Click View File 5) Click blame Repeat as…
git log -L 40,50:app/models/user.rb