issue_comments

Table actions

1 row where issue = 1000164496 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

  • pre-commit: autoupdate hook versions · 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
927879014 https://github.com/pydata/xarray/pull/5799#issuecomment-927879014 https://api.github.com/repos/pydata/xarray/issues/5799 IC_kwDOAMm_X843Tk9m keewis 14808389 2021-09-27T13:31:44Z 2021-09-27T13:31:44Z MEMBER

the caveat with these pre-commit PRs is that the one merging it has to also make sure to delete the branch, otherwise the CI will keeping opening new PRs using that branch.

It would be good to change the CI so it doesn't do that (or have it clean up the existing branches without PRs first), but I don't know how. If nobody can figure it out, I'm sure we can add a warning to the PR message.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   pre-commit: autoupdate hook versions 1000164496

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