issue_comments

Table actions

4 rows where issue = 609950090 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

author_association 2

issue 1

  • Fall back to authentication via ENV · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
622997410 https://github.com/dogsheep/github-to-sqlite/issues/33#issuecomment-622997410 https://api.github.com/repos/dogsheep/github-to-sqlite/issues/33 MDEyOklzc3VlQ29tbWVudDYyMjk5NzQxMA== simonw 9599 2020-05-02T18:46:10Z 2020-05-02T18:46:10Z MEMBER 
{
    "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  
622279374 https://github.com/dogsheep/github-to-sqlite/issues/33#issuecomment-622279374 https://api.github.com/repos/dogsheep/github-to-sqlite/issues/33 MDEyOklzc3VlQ29tbWVudDYyMjI3OTM3NA== garethr 2029 2020-05-01T07:12:47Z 2020-05-01T07:12:47Z NONE

I also go it working with:

yaml run: echo ${{ secrets.github_token }} | github-to-sqlite auth

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Fall back to authentication via ENV 609950090  
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 auth.json mechanism this uses is standard across all of the other Dogsheep tools - it's actually designed so you can have one auth.json with a bunch of different credentials for different tools:

json { "goodreads_personal_token": "...", "goodreads_user_id": "...", "github_personal_token": "...", "pocket_consumer_key": "...", "pocket_username": "...", "pocket_access_token": "..." } But... github-to-sqlite does feel like it deserves a special case here, since it's such a good fit for running inside of GitHub Actions - which even provide a GITHUB_TOKEN for you to use!

So I don't think it will harm the family of tools too much if this has an environment variable alternative to the -a file.

 
{
    "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  

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