issue_comments

Table actions

1 row where issue = 1076265104 and user = 61977 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • seberg · 1 ✖

issue 1

  • Weighted quantile · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1022419678 https://github.com/pydata/xarray/pull/6059#issuecomment-1022419678 https://api.github.com/repos/pydata/xarray/issues/6059 IC_kwDOAMm_X8488OLe seberg 61977 2022-01-26T17:22:40Z 2022-01-26T17:49:18Z NONE

We discussed this in the Triage meeting a bit, and settled on "we want this". We are OK with the sorting approach and limiting e.g. only to aweights, that may need settling 100%, but generally using aweights (and maybe fweights) sems good.

EDIT: Oops, meant to post on the NumPy PR, but OK here as well, I guess ;)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Weighted quantile 1076265104

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);