issue_comments
5 rows where issue = 628003707
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 |
---|---|---|---|---|---|---|---|---|---|---|---|
636510838 | https://github.com/simonw/datasette/issues/784#issuecomment-636510838 | https://api.github.com/repos/simonw/datasette/issues/784 | MDEyOklzc3VlQ29tbWVudDYzNjUxMDgzOA== | simonw 9599 | 2020-05-31T18:39:08Z | 2020-05-31T18:39:08Z | OWNER | I'm calling this the `root` account now, for reasons discussed in these two comments: https://github.com/simonw/datasette/issues/699#issuecomment-636510647 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Ability to sign in to Datasette as a root account 628003707 | |
636514974 | https://github.com/simonw/datasette/issues/784#issuecomment-636514974 | https://api.github.com/repos/simonw/datasette/issues/784 | MDEyOklzc3VlQ29tbWVudDYzNjUxNDk3NA== | simonw 9599 | 2020-05-31T19:12:48Z | 2020-05-31T19:12:48Z | OWNER | For the first version of this I'm not going to use passwords at all. I'll implement this: $ datasette fixtures.db --root The `--root` option will cause Datasette to output a URL with a one-time-use token in it which, when clicked, will authenticate the user as the root account (by setting a signed cookie). Signed cookie means Datasette needs a secrets recipe. I'll open a new issue for that. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Ability to sign in to Datasette as a root account 628003707 | |
636554258 | https://github.com/simonw/datasette/issues/784#issuecomment-636554258 | https://api.github.com/repos/simonw/datasette/issues/784 | MDEyOklzc3VlQ29tbWVudDYzNjU1NDI1OA== | simonw 9599 | 2020-06-01T00:21:33Z | 2020-06-01T00:21:33Z | OWNER | The URL for this will be: `/-/auth-token?token=xxx` The token will be generated by Datasette on startup and will only be valid for a single request, at which point it will be used to set a signed `ds_actor` cookie and then redirect to the homepage. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Ability to sign in to Datasette as a root account 628003707 | |
636565242 | https://github.com/simonw/datasette/issues/784#issuecomment-636565242 | https://api.github.com/repos/simonw/datasette/issues/784 | MDEyOklzc3VlQ29tbWVudDYzNjU2NTI0Mg== | simonw 9599 | 2020-06-01T01:18:20Z | 2020-06-01T01:18:20Z | OWNER | I'm considering this done. I'm going to leave it to plugins to implement a web-based sign-in flow for accounts (at least for the moment). | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Ability to sign in to Datasette as a root account 628003707 | |
654424704 | https://github.com/simonw/datasette/issues/784#issuecomment-654424704 | https://api.github.com/repos/simonw/datasette/issues/784 | MDEyOklzc3VlQ29tbWVudDY1NDQyNDcwNA== | simonw 9599 | 2020-07-06T19:31:53Z | 2020-07-06T19:31:53Z | OWNER | Documentation: https://datasette.readthedocs.io/en/stable/authentication.html#using-the-root-actor | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Ability to sign in to Datasette as a root account 628003707 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);