issue_comments
2 rows where author_association = "MEMBER", issue = 713834297 and user = 10194086 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Allow skipna in .dot() · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 706140256 | https://github.com/pydata/xarray/issues/4482#issuecomment-706140256 | https://api.github.com/repos/pydata/xarray/issues/4482 | MDEyOklzc3VlQ29tbWVudDcwNjE0MDI1Ng== | mathause 10194086 | 2020-10-09T12:01:37Z | 2020-10-09T12:01:37Z | MEMBER |
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Allow skipna in .dot() 713834297 | |
| 702965721 | https://github.com/pydata/xarray/issues/4482#issuecomment-702965721 | https://api.github.com/repos/pydata/xarray/issues/4482 | MDEyOklzc3VlQ29tbWVudDcwMjk2NTcyMQ== | mathause 10194086 | 2020-10-02T21:27:33Z | 2020-10-02T21:27:33Z | MEMBER | Yes that would be very helpful. This is used for the weighted operations: and it would be great if this could be done upstream. However, |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Allow skipna in .dot() 713834297 |
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