issue_comments
2 rows where issue = 1580266844 and user = 2448579 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- use numpys SupportsDtype · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1450808780 | https://github.com/pydata/xarray/pull/7521#issuecomment-1450808780 | https://api.github.com/repos/pydata/xarray/issues/7521 | IC_kwDOAMm_X85WeZXM | dcherian 2448579 | 2023-03-01T20:33:36Z | 2023-03-01T20:33:36Z | MEMBER | Ugh I think I clicked merge too early. Shall we just keep it on our end till it become public? I defer to your judgement here. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
use numpys SupportsDtype 1580266844 | |
| 1449079384 | https://github.com/pydata/xarray/pull/7521#issuecomment-1449079384 | https://api.github.com/repos/pydata/xarray/issues/7521 | IC_kwDOAMm_X85WXzJY | dcherian 2448579 | 2023-02-28T23:23:41Z | 2023-02-28T23:23:41Z | MEMBER | Thanks @headtr1ck Do you know if there's a plan to make something like this public on the numpy end? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
use numpys SupportsDtype 1580266844 |
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