issues

Table actions

6 rows where repo = 213286752, state = "closed" and type = "issue" sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: user, comments, author_association, created_at (date), updated_at (date), closed_at (date)

type 1

  • issue · 6 ✖

state 1

  • closed · 6 ✖

repo 1

  • pocket-to-sqlite · 6 ✖
id node_id number title user state locked assignee milestone comments created_at updated_at ▲ closed_at author_association pull_request body repo type active_lock_reason performed_via_github_app reactions draft state_reason
1795187493 I_kwDODLZ_YM5rAGMl 12 Switch to pyproject.toml simonw 9599 closed 0     2 2023-07-09T01:06:56Z 2023-07-09T01:19:43Z 2023-07-09T01:19:42Z MEMBER   pocket-to-sqlite 213286752 issue     
{
    "url": "https://api.github.com/repos/dogsheep/pocket-to-sqlite/issues/12/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
1246826792 I_kwDODLZ_YM5KUREo 10 When running `auth` command, don't overwrite an existing auth.json file ashanan 11887 closed 0     3 2022-05-24T16:42:20Z 2022-09-07T15:07:38Z 2022-08-22T16:17:19Z NONE  

Ran the auth command in the same directory I'd previously set up an auth.json file for twitter-to-sqlite and it was completely overwritten. Not the biggest issue, but still unexpected. Ideally, for me, the keys would just be added to the existing file, but getting a warning and a chance to back out would be a good solution as well.

 pocket-to-sqlite 213286752 issue     
{
    "url": "https://api.github.com/repos/dogsheep/pocket-to-sqlite/issues/10/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
1345452427 I_kwDODLZ_YM5QMfmL 11 -a option is used for "--auth" and for "--all" fernand0 2467 closed 0     3 2022-08-21T10:50:48Z 2022-08-21T21:11:57Z 2022-08-21T21:11:57Z NONE  

I'm not sure which option is best, instead of -a -all.

 pocket-to-sqlite 213286752 issue     
{
    "url": "https://api.github.com/repos/dogsheep/pocket-to-sqlite/issues/11/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
503234169 MDU6SXNzdWU1MDMyMzQxNjk= 2 Track and use the 'since' value simonw 9599 closed 0     3 2019-10-07T05:02:59Z 2020-03-27T22:22:30Z 2020-03-27T22:22:30Z MEMBER  

Pocket says:

Whenever possible, you should use the since parameter, or count and and offset parameters when retrieving a user's list. After retrieving the list, you should store the current time (which is provided along with the list response) and pass that in the next request for the list. This way the server only needs to return a small set (changes since that time) instead of the user's entire list every time.

At the bottom of https://getpocket.com/developer/docs/v3/retrieve

 pocket-to-sqlite 213286752 issue     
{
    "url": "https://api.github.com/repos/dogsheep/pocket-to-sqlite/issues/2/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
503233021 MDU6SXNzdWU1MDMyMzMwMjE= 1 Use better pagination (and implement progress bar) simonw 9599 closed 0     4 2019-10-07T04:58:11Z 2020-03-27T22:13:57Z 2020-03-27T22:13:57Z MEMBER  

Right now we attempt to load everything at once - which caps out at 5,000 items and is really slow.

We can do better by implementing pagination using count and offset.

 pocket-to-sqlite 213286752 issue     
{
    "url": "https://api.github.com/repos/dogsheep/pocket-to-sqlite/issues/1/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed
589402939 MDU6SXNzdWU1ODk0MDI5Mzk= 4 Store authentication information as "pocket_access_token" etc simonw 9599 closed 0     0 2020-03-27T20:43:22Z 2020-03-27T20:43:59Z 2020-03-27T20:43:59Z MEMBER  

The pocket_ prefix will mean that the same auth.json file can be used for other Dogsheep tools without Pocket over-riding a value set by some other tool.

 pocket-to-sqlite 213286752 issue     
{
    "url": "https://api.github.com/repos/dogsheep/pocket-to-sqlite/issues/4/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issues] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [state] TEXT,
   [locked] INTEGER,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [comments] INTEGER,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [author_association] TEXT,
   [pull_request] TEXT,
   [body] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] TEXT
, [active_lock_reason] TEXT, [performed_via_github_app] TEXT, [reactions] TEXT, [draft] INTEGER, [state_reason] TEXT);
CREATE INDEX [idx_issues_repo]
                ON [issues] ([repo]);
CREATE INDEX [idx_issues_milestone]
                ON [issues] ([milestone]);
CREATE INDEX [idx_issues_assignee]
                ON [issues] ([assignee]);
CREATE INDEX [idx_issues_user]
                ON [issues] ([user]);