issue_comments

Table actions

1 row where issue = 1423347412

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

id ▼ html_url issue_url node_id user created_at updated_at author_association body reactions issue performed_via_github_app
1291418546 https://github.com/simonw/datasette/issues/1857#issuecomment-1291418546 https://api.github.com/repos/simonw/datasette/issues/1857 IC_kwDOBm6k_c5M-Xuy simonw 9599 2022-10-26T02:38:35Z 2022-10-26T02:38:35Z OWNER I'm going to set a convention that an actor signed in via a token should set `"token": "something"` as a key. Then the `/-/create-token` view can reject those actors. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Prevent API tokens from using /-/create-token to create more tokens 1423347412  

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,
   [issue] INTEGER REFERENCES [issues]([id])
, [performed_via_github_app] TEXT);
CREATE INDEX [idx_issue_comments_issue]
                ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
                ON [issue_comments] ([user]);