issue_comments

Table actions

1 row where author_association = "COLLABORATOR" and issue = 1419825696 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

issue 1

  • Deprecate cfgrib backend · 1 ✖

author_association 1

  • COLLABORATOR · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1464331562 https://github.com/pydata/xarray/issues/7199#issuecomment-1464331562 https://api.github.com/repos/pydata/xarray/issues/7199 IC_kwDOAMm_X85XR-0q headtr1ck 43316012 2023-03-10T19:49:10Z 2023-03-10T19:49:10Z COLLABORATOR

Any ideas on how to deprecate this? Do we raise a Deprecation warning if someone uses the open_dataset method of the internal backend? And then remove it some versions down the line?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Deprecate cfgrib backend 1419825696

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