I thought that maybe I was just not used to the interface.
I thought that maybe I just preferred the way I had been doing things.
I thought that maybe I didn’t see the features for the trees.
Over the years, I’ve become very used to Bitbucket’s style of pull requests and the interface that is used to process them. It isn’t perfect, but it is very navigable and generally I like the way it works.
Over the last six to twelve months or so, I’ve been using the Github pull request interface. It is drastically different. Where Bitbucket puts each file in a separate screen. Github puts the each Diff in a continuous layout. You simply scroll through the changes until you have seen all of them.
I think part of the problem is that Bitbucket is focused more on corporate projects begin run internally, while Github is all about open source projects being run by distributed individuals or teams.
Github’s interface is better for small changes and Bitbucket’s seems to be better for large changes. That seems to be the basic driver. Open projects with many developers tend to commit smaller changes in a more organized manner. Private projects, run internally of a company, tend to commit large changes for new or existing features.
I could be totally wrong. It may be that I just don’t know all of the Github features.