issue_comments

Table actions

1 row where issue = 1063049830 and user = 4160723 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

  • benbovy · 1 ✖

issue 1

  • Try new Issue template format? · 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
1048737617 https://github.com/pydata/xarray/issues/6027#issuecomment-1048737617 https://api.github.com/repos/pydata/xarray/issues/6027 IC_kwDOAMm_X84-gndR benbovy 4160723 2022-02-23T12:34:48Z 2022-02-23T12:34:48Z MEMBER

This looks great although in a few exceptional cases I find it a bit annoying, e.g., for meta-issues when none of the available templates really fit, like #6293.

I like this suggestion github/feedback/discussions/9964 but what should we do in the meantime?

  • A. do nothing (we could still fill the form then edit the issue just afterwards)
  • B. add another, very generic template
  • C. enable blank issues with blank_issues_enabled=true

Thoughts? 

{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Try new Issue template format? 1063049830

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