issue_comments

Table actions

1 row where issue = 1637616804 and user = 14808389 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

  • keewis · 1 ✖

issue 1

  • use the `files` interface instead of the deprecated `read_binary` · 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
1481327369 https://github.com/pydata/xarray/pull/7664#issuecomment-1481327369 https://api.github.com/repos/pydata/xarray/issues/7664 IC_kwDOAMm_X85YS0MJ keewis 14808389 2023-03-23T14:46:02Z 2023-03-23T14:54:42Z MEMBER

should we use a released version of actions/labeler? A change to their main branch seems to have broken our workflow, but that's something to be expected, I guess.

Edit: turns out we had a workaround in our workflow, which has been fixed upstream (but broke the workaround). I think we have two options: keep the workaround but use v4, or stay on main and remove the workaround. The latter seems better in the long term, but staying on main involves the risk of unexpected changes.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   use the `files` interface instead of the deprecated `read_binary` 1637616804

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