Link to GitHub issue

[Rudloff]

Hello,

It would be nice to have a link from the webcompat.com issue to the GitHub issue (and vice-versa).

Regards,

[miketaylr]

Hey @Rudloff, good suggestion. Right now we have a (basically hidden) key listener to take you to the GitHub issue page. For example, from http://webcompat.com/issues/44 if you press 'g', it will redirect you to webcompat/web-bugs#44.

But I like the idea of linking back to webcompat.com from the GitHub issue.

[karlcow]

So to move a bit forward with this.

An issue is created by a POST
It returns a 201Created with a Location: header giving the link and a JSON file with the data which have been recorded. We are interested by the body.
We can grab that Location and sends right away from webcompat.com server a PATCH

Let say that we received (cutting some fields for brevity)

HTTP/1.1 201 Created
Location: https://api.github.com/repos/webcompat/webcompat.com/issues/1`

{ "body": 
'URL: http://shinydemos.com/border-salon/
Browser: Firefox
Version: 31 (Nightly)
Problem type: Looks like the website has a bug.
Site owner: No

Steps […]'
}

We can then sends back to github:

PATCH /repos/webcompat/webcompat.com/issues/1 HTTP/1.1
Host: api.github.com

{ "body": 
'URL: http://shinydemos.com/border-salon/
Browser: Firefox
Version: 31 (Nightly)
Problem type: Looks like the website has a bug.
Site owner: No
WebCompat: http://webcompat.com/issues/1

Steps […]'
}

[miketaylr]

Very smart.

Do you think we should hide that info when on the webcompat site?

[karlcow]

Yes and no.
It could be hidden with a parsing on the client side and adding an appropriate display.
It could be left in order for someone to cut and paste the content in an email with all the body information.

[miketaylr]

"cut and paste" seems like a use case we want to support by default. Meaning, we shouldn't try to hide it from webcompat.com side.

[miketaylr]

The link from webcompat.com -> GitHub is solved (via "g" shortcut). GitHub to webcompat.com needs work but should be a separate issue (also needs discussion in terms of design).