issue_comments
2 rows where author_association = "NONE" and issue = 403458737 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Fix CRS being WKT instead of PROJ.4 · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
458259755 | https://github.com/pydata/xarray/pull/2715#issuecomment-458259755 | https://api.github.com/repos/pydata/xarray/issues/2715 | MDEyOklzc3VlQ29tbWVudDQ1ODI1OTc1NQ== | pep8speaks 24736507 | 2019-01-28T19:05:21Z | 2019-02-06T16:49:02Z | NONE | Hello @djhoese! Thanks for updating the PR. Cheers ! There are no PEP8 issues in this Pull Request. :beers: Comment last updated on February 06, 2019 at 16:49 Hours UTC |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix CRS being WKT instead of PROJ.4 403458737 | |
457849358 | https://github.com/pydata/xarray/pull/2715#issuecomment-457849358 | https://api.github.com/repos/pydata/xarray/issues/2715 | MDEyOklzc3VlQ29tbWVudDQ1Nzg0OTM1OA== | sgillies 33697 | 2019-01-26T17:30:22Z | 2019-01-26T21:52:52Z | NONE | @djhoese sorry for the inconvenience! I didn't consider the change in rasterio 1.0.14 to be an API change because the behavior of |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix CRS being WKT instead of PROJ.4 403458737 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [issue] INTEGER REFERENCES [issues]([id]) ); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
user 2