Pull Request Progress Update


I want to give an update on some of the work that’s been going on to prepare moving the project over to GitHub Pull Requests. The most notable thing that’s happened recently is that we submitted a list of feature requests to GitHub. We don’t expect them to be able to implement everything, but we are hopeful that some of the features will make it on their roadback. We’ve heard back that GitHub may want to have conversation with individual community members to clarify some of the requests, so stay tuned on that.

Besides the feature requests, there have been some good discussions on some of the tickets we have concerning pull requests. I would like to highlight just two of the tickets here.

The first is the ticket regarding alternative user interfaces, it would be great if we could get some volunteers to try out some of these third-party interfaces. We can even set up an experimentation repo if that would help.

The second is the ticket concerning pull requests with multiple commits, I believe we’ve come to a consensus, but we need a volunteer to create a blank ‘Pull Request Policies’ document and then record our decision there.

I’m going to try to do updates like this at least once a month, or maybe more frequently if there is a lot of activity. If you think you want to help, take a look at the existing tickets and see what there is left to do.


Hey @tstellar thank you for putting this update together and collecting all the information concisely!

The GitHub project you’re using to track this Pull Request Migration, is marked as Private, so only people with commit access can view it. Is that intentional? I’m sure there are downstream users or other contributors who are interested in seeing the list of issues.

1 Like

As for “alternative user” interfaces. What is the recommended way to try them? Is it OK for people to create a diff on phabricator for visibility, asking to do it at %url% and leave a link for the reference?

I don’t do reviews that often but I can try to e.g. assemble a short document on “how to create a review” in one of them if that will lower the bar to try.

Thanks for letting me know, I’ve made the project public.

This makes sense to me. It might work best if you can find a reviewer who will agree ahead of time to do the review with the “alternative interface”.