issue_comments
2 rows where issue = 1173497454 and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- [FEATURE]: Add a replace method · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1074025301 | https://github.com/pydata/xarray/issues/6377#issuecomment-1074025301 | https://api.github.com/repos/pydata/xarray/issues/6377 | IC_kwDOAMm_X85ABFNV | max-sixty 5635139 | 2022-03-21T15:14:40Z | 2022-03-21T15:14:40Z | MEMBER | Nice find @dcherian . So it sounds like there's consensus around something like You're right about |
{
"total_count": 2,
"+1": 2,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
[FEATURE]: Add a replace method 1173497454 | |
| 1072680183 | https://github.com/pydata/xarray/issues/6377#issuecomment-1072680183 | https://api.github.com/repos/pydata/xarray/issues/6377 | IC_kwDOAMm_X84_78z3 | max-sixty 5635139 | 2022-03-18T18:27:03Z | 2022-03-18T18:27:03Z | MEMBER | I agree this would be useful, and I've had to do similar things. It's the sort of area where pandas is stronger than xarray. We might want a more specific name than @Huite thanks for the great proposal. Did you look at |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
[FEATURE]: Add a replace method 1173497454 |
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