issue_comments
2 rows where user = 4806678 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 927024549 | https://github.com/pydata/xarray/issues/5815#issuecomment-927024549 | https://api.github.com/repos/pydata/xarray/issues/5815 | IC_kwDOAMm_X843QUWl | hrzn 4806678 | 2021-09-25T07:17:19Z | 2021-09-25T07:17:19Z | CONTRIBUTOR |
Done! https://github.com/pydata/xarray/pull/5819 Thanks. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Inconsistent dropping of `DatetimeIndex.freq` attribute from `DataArray`s index. 1006413760 | |
| 926922607 | https://github.com/pydata/xarray/issues/5815#issuecomment-926922607 | https://api.github.com/repos/pydata/xarray/issues/5815 | IC_kwDOAMm_X843P7dv | hrzn 4806678 | 2021-09-24T21:13:03Z | 2021-09-24T21:13:03Z | CONTRIBUTOR | Yes this is a good point. In fact I'm not really willing to change the index in place, but I'm doing so because I've observed that the Btw, we have recently switched to using |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Inconsistent dropping of `DatetimeIndex.freq` attribute from `DataArray`s index. 1006413760 |
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