Page MenuHomePhabricator

Bridge GitHub to Phabricator
Open, NormalPublic

"Love" token, awarded by leoluk."Like" token, awarded by kaendfinger."Love" token, awarded by eduard44."Mountain of Wealth" token, awarded by Luke081515.2."Love" token, awarded by hach-que."The World Burns" token, awarded by johnny-bit."Like" token, awarded by joshuaspence."Grey Medal" token, awarded by nateguchi2."Baby Tequila" token, awarded by chad."Like" token, awarded by michaeljs1990."Love" token, awarded by tycho.tatitscheff."Pterodactyl" token, awarded by cburroughs.
Assigned To
Authored By
epriestley, Mar 7 2016


If we build a tremendously complicated, expensive, difficult-to-maintain bridge between Phabricator and GitHub, it is possible that we will reduce the activation energy required to move a project from GitHub to Phabricator enough to have a substantial impact on growth. Or maybe not.

Our current plan is to build a minimal version of this and see if it gets any traction.

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes
cburroughs added a subscriber: cburroughs.
chad awarded a token.Mar 8 2016, 2:27 AM
Krenair added a subscriber: Krenair.Mar 8 2016, 2:36 PM
johnny-bit added a subscriber: johnny-bit.
chad mentioned this in Roadmap.Mar 8 2016, 9:27 PM

Alright, so here's the first real issue. Here's what I did on GitHub:

I also edited a comment and subscribed/unsubscribed in this sequence.

Here's what the GitHub Events API gives me for that:

That is, I only get the major events (comment, close, reopen).

There's also a separate "Issue Events API", which I haven't looked at yet. So it's possible we can just poll both APIs, which is messy but not especially problematic. I'll see how bad Pull Request-related events look first.

The "Issue Events API" appears to provide the remaining events in a different format with different rules. It does not provide any duplicate events, so, e.g., one API retrieves issues being created and commented on while a different API retrieves labels, milestones, etc., except that both report opens and closes, I think. Anyway, seems mostly workable.

stevex added a subscriber: stevex.Apr 15 2016, 3:07 PM
toebu added a subscriber: toebu.May 9 2016, 9:01 PM
turadg added a subscriber: turadg.May 18 2016, 4:20 PM

Will this be a one way or two way bridge?

urzds added a subscriber: urzds.Sep 8 2016, 6:09 AM

Where does this feature stand? I wasn't able to find any documentation on how to use this, but it also looks that a non-trivial amount of work has been completed towards this goal. Is this something still in the immediate roadmap? Being able to easily integrate GitHub issues into Phabricator (and back) is a big roadblock to adoption for us.

See Planning for help with timelines and status.

chad added a subscriber: chad.Feb 13 2017, 9:10 PM

Hard to say since it fell off the roadmap a year ago, but we do have rough plans to ship Nuance (pre-requisite) in the shorter term.

hskiba added a subscriber: hskiba.Mar 21 2017, 2:38 AM
epriestley moved this task from v1 to Backlog on the Nuance board.May 21 2017, 12:43 PM
epriestley edited projects, added Nuance; removed Nuance (v1).
revi added a subscriber: revi.Jan 17 2018, 11:30 AM