issue_comments
3 rows where author_association = "MEMBER" and issue = 712247862 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- WIP: Proposed refactor of read API for backends · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
714559908 | https://github.com/pydata/xarray/pull/4477#issuecomment-714559908 | https://api.github.com/repos/pydata/xarray/issues/4477 | MDEyOklzc3VlQ29tbWVudDcxNDU1OTkwOA== | shoyer 1217238 | 2020-10-22T15:07:33Z | 2020-10-22T15:07:33Z | MEMBER | Merging per offline discussion. This is all hidden behind an environment variable, so this will allow @aurghs and @alexamici to continue working on these new features. |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
WIP: Proposed refactor of read API for backends 712247862 | |
704059832 | https://github.com/pydata/xarray/pull/4477#issuecomment-704059832 | https://api.github.com/repos/pydata/xarray/issues/4477 | MDEyOklzc3VlQ29tbWVudDcwNDA1OTgzMg== | shoyer 1217238 | 2020-10-06T06:28:58Z | 2020-10-06T06:28:58Z | MEMBER | I really like the direction this is going! See https://github.com/pydata/xarray/issues/4490 for a related design proposal, that could build on top of this (and/or potentially make this easier). |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
WIP: Proposed refactor of read API for backends 712247862 | |
701622370 | https://github.com/pydata/xarray/pull/4477#issuecomment-701622370 | https://api.github.com/repos/pydata/xarray/issues/4477 | MDEyOklzc3VlQ29tbWVudDcwMTYyMjM3MA== | alexamici 226037 | 2020-09-30T20:19:21Z | 2020-09-30T20:19:21Z | MEMBER | Note that this PR doesn't change xarray behaviour unless the user sets the environment variable To test the new code paths you can use: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
WIP: Proposed refactor of read API for backends 712247862 |
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