issue_comments
2 rows where issue = 532373563 and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date)
issue 1
- Silence sphinx warnings: Round 2 · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 562542618 | https://github.com/pydata/xarray/pull/3592#issuecomment-562542618 | https://api.github.com/repos/pydata/xarray/issues/3592 | MDEyOklzc3VlQ29tbWVudDU2MjU0MjYxOA== | max-sixty 5635139 | 2019-12-06T11:48:35Z | 2019-12-06T11:48:35Z | MEMBER | Looks great!! Really good that we can enforce the warnings from here (I'm on vacation so forgive the lack of engagement) |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Silence sphinx warnings: Round 2 532373563 | |
| 561461567 | https://github.com/pydata/xarray/pull/3592#issuecomment-561461567 | https://api.github.com/repos/pydata/xarray/issues/3592 | MDEyOklzc3VlQ29tbWVudDU2MTQ2MTU2Nw== | max-sixty 5635139 | 2019-12-04T03:35:06Z | 2019-12-04T03:35:06Z | MEMBER | Great!! Will be good to get CI up & running. Should we add that as part of this PR? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Silence sphinx warnings: Round 2 532373563 |
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