Funny but Azure Repos actually has had this feature for a while. When I first joined Microsoft I was shocked that all our teams used Azure Repos instead of GitHub considering we own GitHub but as I've used Repos more and more I've actually come to like it more than GitHub itself. A lot of the UI is cleaner and more intuitive than GitHub to me now, maybe just from using it a lot.
Pull Request File Tree Feedback
41–50 of 77 posts
Re: Pull Request File Tree Feedback
#42Earlier quoted context omitted.
Might be worth making a bounty for it in refined github[0], similar things have been implemented in the past[1] [0] https://github.com/refined-github/refined-github [1] https://github.com/refined-github/refined-github/issues/2151
An extension shouldn't be needed for a dev-centric service like GH to be usable. This is the wrong way to fight bad UX, as it's ridiculous to make installation of a potential security vulnerability of an addon necessary to make a git-frontend website work well. Better to just find a dev-first platform instead.
Re: Pull Request File Tree Feedback
#43Earlier quoted context omitted.
An extension shouldn't be needed for a dev-centric service like GH to be usable. This is the wrong way to fight bad UX, as it's ridiculous to make installation of a potential security vulnerability of an addon necessary to make a git-frontend website work well. Better to just find a dev-first platform instead.
Seriously. If they’re too busy making sketchy copyright decisions with their AI code generation to bother with basic usable UI, they don’t deserve to be the de facto home of open source. I’ve been giving sourcehut a try, and the simplicity is refreshing.
Re: Pull Request File Tree Feedback
#44I’d settle for them making PRs as useful as they were in 2015, before they messed up some of the most basic functionality: showing the diff, and showing review comments. They hide big diffs behind a “load more” link, and as a result people often fail to code review the most substantial part of a change because they scan right past it, thinking it’s a removed file or binary or something. Then, once you submit a review…
Maybe they're trying to nudge us towards smaller PRs. Many reviewers gloss over 300+ line changes in a single file. Approved with a "LGTM" and no further comment, but perhaps that's more a cultural issue with the team than anything.
Re: Pull Request File Tree Feedback
#45I’d settle for them making PRs as useful as they were in 2015, before they messed up some of the most basic functionality: showing the diff, and showing review comments. They hide big diffs behind a “load more” link, and as a result people often fail to code review the most substantial part of a change because they scan right past it, thinking it’s a removed file or binary or something. Then, once you submit a review…
Additionally, the notification email links to "View it on GitHub" don't reliably cause the relevant parts of the page to expand so you end up wading through a huge PR expanding things at random until you find the message.
Re: Pull Request File Tree Feedback
#46We've had a file tree for some time now (along with some of the other feedback I'm seeing in this thread, large diffs etc).
If anyone wants to give it a spin, happy to give you an invite :)
Re: Pull Request File Tree Feedback
#47Earlier quoted context omitted.
Might be worth making a bounty for it in refined github[0], similar things have been implemented in the past[1] [0] https://github.com/refined-github/refined-github [1] https://github.com/refined-github/refined-github/issues/2151
An extension shouldn't be needed for a dev-centric service like GH to be usable. This is the wrong way to fight bad UX, as it's ridiculous to make installation of a potential security vulnerability of an addon necessary to make a git-frontend website work well. Better to just find a dev-first platform instead.
Re: Pull Request File Tree Feedback
#48One of the few things worth actually stealing from BitBucket. Lol
Since GitHub is owned by Microsoft and their other product has had this, I’m guessing it’s yet another copy-over like GitHub Actions was from Azure Pipelines. Not sure how long it’s been in AzureDevOps but it could have been inspired from GitLab there I suppose.
Re: Pull Request File Tree Feedback
#49I’d settle for them making PRs as useful as they were in 2015, before they messed up some of the most basic functionality: showing the diff, and showing review comments. They hide big diffs behind a “load more” link, and as a result people often fail to code review the most substantial part of a change because they scan right past it, thinking it’s a removed file or binary or something. Then, once you submit a review…
Maybe they're trying to nudge us towards smaller PRs. Many reviewers gloss over 300+ line changes in a single file. Approved with a "LGTM" and no further comment, but perhaps that's more a cultural issue with the team than anything.
Unfortunately there are a massive number of codebases where a "simple" change can mean changing _lots_ of places.