issue_comments

Table actions

1 row where issue = 806436724 and user = 5635139 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

  • max-sixty · 1 ✖

issue 1

  • release 0.17.0 · 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
778447800 https://github.com/pydata/xarray/issues/4894#issuecomment-778447800 https://api.github.com/repos/pydata/xarray/issues/4894 MDEyOklzc3VlQ29tbWVudDc3ODQ0NzgwMA== max-sixty 5635139 2021-02-12T20:50:52Z 2021-02-12T20:50:52Z MEMBER

Unless we're really confident that a feature is a few days away, I'd vote to generally proceed with releases. Releases are fairly cheap to do now (and I'm happy to do them), and uncoupling parts of the process lets it move faster.

Ofc if we have regressions, then we should solve those. (I have been under a crunch recently but can hopefully help more in a week or so)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   release 0.17.0 806436724

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