31–40 of 49 posts
maybe there's a quick way to do this but i would like a way to find a git commit, and trace it to the people that approved a PR that got it into the default branch. it'd make my life easier to know who let the bug into prod
I wish gitlens was in the GitHub.dev environment. I use it's like blame all the time!
A 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…
Here is how you can do this via the commandline for one or more lines: git log -L 40,50:app/models/user.rb
I’d like to see fine grained control over what PR notifications I get. Let me unsubscribe from notifications for some of the teams I’m on but don’t need to directly review. This would make it easier for me to help my day-to-day team be more productive. But… that’s probably not in scope for your tool.
A 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…
Earlier quoted context omitted.
Here is how you can do this via the commandline for one or more lines: git log -L 40,50:app/models/user.rb
I think that will lose track of what you're really after if the function changes enough, or is moved to a different part of the file, or just moved out. Without tools that understand the code (e.g. AI) git alone can't keep track of changes the way humans do.
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.
Hmm, I don't think that I would want a GitHub productivity tool. The experience is already pretty optimal for PRs and code review. In terms of things within the development lifecycle that would need their productivity boosted, GitHub isn't close to the top of the list for me.