issue_comments
2 rows where issue = 655282530 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Add release summary, some touch-ups · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 663071648 | https://github.com/pydata/xarray/pull/4217#issuecomment-663071648 | https://api.github.com/repos/pydata/xarray/issues/4217 | MDEyOklzc3VlQ29tbWVudDY2MzA3MTY0OA== | dcherian 2448579 | 2020-07-23T15:26:36Z | 2020-07-23T15:26:36Z | MEMBER | Thanks @max-sixty |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Add release summary, some touch-ups 655282530 | |
| 657260000 | https://github.com/pydata/xarray/pull/4217#issuecomment-657260000 | https://api.github.com/repos/pydata/xarray/issues/4217 | MDEyOklzc3VlQ29tbWVudDY1NzI2MDAwMA== | max-sixty 5635139 | 2020-07-12T18:43:40Z | 2020-07-12T18:43:40Z | MEMBER | Updated based on @keewis good suggestions. I haven't updated the numbers until we agree it's correct. (Maybe there's some plugin to do this? Lucky we don't have a 100 item list...) |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Add release summary, some touch-ups 655282530 |
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