issue_comments
2 rows where author_association = "MEMBER", issue = 432019600 and user = 6815844 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Safely open / close netCDF files without resource locking · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
485962269 | https://github.com/pydata/xarray/issues/2887#issuecomment-485962269 | https://api.github.com/repos/pydata/xarray/issues/2887 | MDEyOklzc3VlQ29tbWVudDQ4NTk2MjI2OQ== | fujiisoup 6815844 | 2019-04-23T20:30:02Z | 2019-04-23T20:30:02Z | MEMBER |
Yes, that is actually in my mind. I added a tag |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Safely open / close netCDF files without resource locking 432019600 | |
482783365 | https://github.com/pydata/xarray/issues/2887#issuecomment-482783365 | https://api.github.com/repos/pydata/xarray/issues/2887 | MDEyOklzc3VlQ29tbWVudDQ4Mjc4MzM2NQ== | fujiisoup 6815844 | 2019-04-13T07:05:24Z | 2019-04-13T07:05:24Z | MEMBER | I didn't notice that I personally want to a simpler function for the daily (not so big data) analysis without caring open / close stuff.
(and probably also for new users)
Is it too much if we add |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Safely open / close netCDF files without resource locking 432019600 |
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 1