issue_comments
10 rows where reactions = "{"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}", "updated_at" is on date 2020-04-30 and user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- simonw · 10 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
622171097 | https://github.com/dogsheep/github-to-sqlite/issues/33#issuecomment-622171097 | https://api.github.com/repos/dogsheep/github-to-sqlite/issues/33 | MDEyOklzc3VlQ29tbWVudDYyMjE3MTA5Nw== | simonw 9599 | 2020-04-30T23:22:45Z | 2020-04-30T23:23:57Z | MEMBER | The
So I don't think it will harm the family of tools too much if this has an environment variable alternative to the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fall back to authentication via ENV 609950090 | |
622169728 | https://github.com/dogsheep/github-to-sqlite/issues/33#issuecomment-622169728 | https://api.github.com/repos/dogsheep/github-to-sqlite/issues/33 | MDEyOklzc3VlQ29tbWVudDYyMjE2OTcyOA== | simonw 9599 | 2020-04-30T23:18:51Z | 2020-04-30T23:18:51Z | MEMBER | Sure, that sounds fine to me. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fall back to authentication via ENV 609950090 | |
622135654 | https://github.com/dogsheep/github-to-sqlite/issues/34#issuecomment-622135654 | https://api.github.com/repos/dogsheep/github-to-sqlite/issues/34 | MDEyOklzc3VlQ29tbWVudDYyMjEzNTY1NA== | simonw 9599 | 2020-04-30T21:53:44Z | 2020-04-30T21:56:06Z | MEMBER | I think this is the neatest scraping pattern:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Command for retrieving dependents for a repo 610408908 | |
622136585 | https://github.com/dogsheep/github-to-sqlite/issues/34#issuecomment-622136585 | https://api.github.com/repos/dogsheep/github-to-sqlite/issues/34 | MDEyOklzc3VlQ29tbWVudDYyMjEzNjU4NQ== | simonw 9599 | 2020-04-30T21:55:51Z | 2020-04-30T21:55:51Z | MEMBER | And to find the "Next" pagination link:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Command for retrieving dependents for a repo 610408908 | |
622133775 | https://github.com/dogsheep/github-to-sqlite/issues/34#issuecomment-622133775 | https://api.github.com/repos/dogsheep/github-to-sqlite/issues/34 | MDEyOklzc3VlQ29tbWVudDYyMjEzMzc3NQ== | simonw 9599 | 2020-04-30T21:49:27Z | 2020-04-30T21:49:27Z | MEMBER | Proposed command:
I'll pull full details of the scraped repos from the regular API. I'll also record when they were "first seen" by the command. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Command for retrieving dependents for a repo 610408908 | |
622133422 | https://github.com/dogsheep/github-to-sqlite/issues/34#issuecomment-622133422 | https://api.github.com/repos/dogsheep/github-to-sqlite/issues/34 | MDEyOklzc3VlQ29tbWVudDYyMjEzMzQyMg== | simonw 9599 | 2020-04-30T21:48:39Z | 2020-04-30T21:48:39Z | MEMBER | It looks like the only option is to scrape them. I'll do that and then replace with an API as soon as one becomes available. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Command for retrieving dependents for a repo 610408908 | |
622043887 | https://github.com/simonw/datasette/issues/747#issuecomment-622043887 | https://api.github.com/repos/simonw/datasette/issues/747 | MDEyOklzc3VlQ29tbWVudDYyMjA0Mzg4Nw== | simonw 9599 | 2020-04-30T19:04:19Z | 2020-04-30T19:04:19Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Directory configuration mode should support metadata.yaml 610192152 | ||
622036934 | https://github.com/simonw/datasette/issues/747#issuecomment-622036934 | https://api.github.com/repos/simonw/datasette/issues/747 | MDEyOklzc3VlQ29tbWVudDYyMjAzNjkzNA== | simonw 9599 | 2020-04-30T18:51:18Z | 2020-04-30T18:51:18Z | OWNER | Needs docs. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Directory configuration mode should support metadata.yaml 610192152 | |
622003376 | https://github.com/simonw/datasette/issues/747#issuecomment-622003376 | https://api.github.com/repos/simonw/datasette/issues/747 | MDEyOklzc3VlQ29tbWVudDYyMjAwMzM3Ng== | simonw 9599 | 2020-04-30T17:45:32Z | 2020-04-30T17:45:32Z | OWNER | I can use this function to load the JSON-or-YAML: https://github.com/simonw/datasette/blob/d349d57cdf3d577afb62bdf784af342a4d5be660/datasette/utils/init.py#L798-L806 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Directory configuration mode should support metadata.yaml 610192152 | |
621948898 | https://github.com/simonw/datasette/issues/747#issuecomment-621948898 | https://api.github.com/repos/simonw/datasette/issues/747 | MDEyOklzc3VlQ29tbWVudDYyMTk0ODg5OA== | simonw 9599 | 2020-04-30T16:05:50Z | 2020-04-30T16:05:50Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Directory configuration mode should support metadata.yaml 610192152 |
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]);
issue 3