issue_comments

Table actions

2 rows where author_association = "MEMBER" and issue = 611284481 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

issue 1

  • [Feature Request] Support Repo Name in Search 🥺 · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
623038378 https://github.com/dogsheep/github-to-sqlite/issues/38#issuecomment-623038378 https://api.github.com/repos/dogsheep/github-to-sqlite/issues/38 MDEyOklzc3VlQ29tbWVudDYyMzAzODM3OA== simonw 9599 2020-05-03T01:21:13Z 2020-05-03T01:21:13Z MEMBER

No this is really useful feedback! I'm so close to this project that I miss what's not obvious to people dropping in for the first time.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 [Feature Request] Support Repo Name in Search 🥺 611284481  
623027889 https://github.com/dogsheep/github-to-sqlite/issues/38#issuecomment-623027889 https://api.github.com/repos/dogsheep/github-to-sqlite/issues/38 MDEyOklzc3VlQ29tbWVudDYyMzAyNzg4OQ== simonw 9599 2020-05-02T23:15:11Z 2020-05-02T23:15:11Z MEMBER

This is one of the use-cases for the repos_starred view: it allows you to easily run this kid of query without having to construct the SQL by hand. Here's a demo:

https://github-to-sqlite.dogsheep.net/github/repos_starred?name__contains=twitter

My philosophy here is to keep the raw tables (like stars) as normalized as possible, then use SQL views which expose the data in a form that's easier to query.

 
{
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 1,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 [Feature Request] Support Repo Name in Search 🥺 611284481  

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