issue_comments

Table actions

where issue = 1178949620 and user = 5635139 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • max-sixty · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1077888555 https://github.com/pydata/xarray/issues/6408#issuecomment-1077888555 https://api.github.com/repos/pydata/xarray/issues/6408 IC_kwDOAMm_X85AP0Yr max-sixty 5635139 2022-03-24T17:53:25Z 2022-03-24T17:53:25Z MEMBER

@shoyer do you think we need a deprecation cycle for those in https://github.com/pydata/xarray/pull/6403? It would be less work if we didn't.

I was thinking that for some of them we did need a depr. cycle, but only because I've seen many cases where specific methods don't use kwargs — e.g. .diff(dim, 2). WDYT?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   backwards incompatible changes in reductions 1178949620

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