issue_comments
2 rows where issue = 1094753761 and user = 6628425 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- [FEATURE]: allow "now" as input to cftime_range · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1007815885 | https://github.com/pydata/xarray/issues/6143#issuecomment-1007815885 | https://api.github.com/repos/pydata/xarray/issues/6143 | IC_kwDOAMm_X848EgzN | spencerkclark 6628425 | 2022-01-07T23:23:02Z | 2022-01-07T23:23:02Z | MEMBER | Something that might make this easier would be to implement a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
[FEATURE]: allow "now" as input to cftime_range 1094753761 | |
1006524761 | https://github.com/pydata/xarray/issues/6143#issuecomment-1006524761 | https://api.github.com/repos/pydata/xarray/issues/6143 | IC_kwDOAMm_X847_llZ | spencerkclark 6628425 | 2022-01-06T12:01:07Z | 2022-01-06T12:06:31Z | MEMBER | This seems reasonable. We would probably only enable it for real-world calendars, i.e. |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
[FEATURE]: allow "now" as input to cftime_range 1094753761 |
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