issue_comments

Table actions

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

  • Relax GitHub Actions first time contributor approval? · 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
958192851 https://github.com/pydata/xarray/issues/5928#issuecomment-958192851 https://api.github.com/repos/pydata/xarray/issues/5928 IC_kwDOAMm_X845HNzT keewis 14808389 2021-11-02T21:44:54Z 2021-11-02T21:44:54Z MEMBER

I just changed that setting. In the first place, that restriction was put in place to avoid cryptominers being run in CI, so if we get any strange PRs we'll have to revert.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Relax GitHub Actions first time contributor approval? 1042698589

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