issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 552994673 and user = 5635139 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • max-sixty · 1 ✖

issue 1

  • bump min deps for 0.15 · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
578295750 https://github.com/pydata/xarray/pull/3713#issuecomment-578295750 https://api.github.com/repos/pydata/xarray/issues/3713 MDEyOklzc3VlQ29tbWVudDU3ODI5NTc1MA== max-sixty 5635139 2020-01-24T20:48:46Z 2020-01-24T20:48:46Z MEMBER

For sure no harm in keeping older ones for this release. But to the extent we can have a policy we agree on, then it's not a judgement call each release. Should we change the policy?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   bump min deps for 0.15 552994673

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