issue_comments

Table actions

1 row where issue = 735267574 and user = 10194086 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

  • mathause · 1 ✖

issue 1

  • rm inplace arg to rename · 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
721845992 https://github.com/pydata/xarray/pull/4561#issuecomment-721845992 https://api.github.com/repos/pydata/xarray/issues/4561 MDEyOklzc3VlQ29tbWVudDcyMTg0NTk5Mg== mathause 10194086 2020-11-04T16:47:26Z 2020-11-04T16:47:26Z MEMBER

This was in 0.13 http://xarray.pydata.org/en/stable/whats-new.html#v0-13-0-17-sep-2019 I actually don't know if we have an official policy for deprecations? Two major versions?

Should all of these checks be removed? #3260

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   rm inplace arg to rename 735267574

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