issue_comments
2 rows where issue = 874231291 and user = 14808389 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date)
issue 1
- Fix bulleted list indentation in docstrings · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
832139447 | https://github.com/pydata/xarray/pull/5250#issuecomment-832139447 | https://api.github.com/repos/pydata/xarray/issues/5250 | MDEyOklzc3VlQ29tbWVudDgzMjEzOTQ0Nw== | keewis 14808389 | 2021-05-04T18:08:22Z | 2021-05-04T18:09:00Z | MEMBER |
no, I didn't.
I'll need to investigate more, but I think we should probably do that soon. There should be standard rst linters, too, but those might need more configuration: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix bulleted list indentation in docstrings 874231291 | |
831447687 | https://github.com/pydata/xarray/pull/5250#issuecomment-831447687 | https://api.github.com/repos/pydata/xarray/issues/5250 | MDEyOklzc3VlQ29tbWVudDgzMTQ0NzY4Nw== | keewis 14808389 | 2021-05-03T18:31:14Z | 2021-05-03T18:31:14Z | MEMBER | the initial issue, at least, would have been caught by |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix bulleted list indentation in docstrings 874231291 |
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