issues

Table actions

2 rows where state = "closed", type = "pull" and user = 48517 sorted by updated_at descending

✖
✖
✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

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

type 1

  • pull · 2 ✖

state 1

  • closed · 2 ✖

repo 1

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
374675798 MDExOlB1bGxSZXF1ZXN0MjI2MzE0ODYy 367 Mark codemirror files as vendored jaap3 48517 closed 0     2 2018-10-27T18:41:25Z 2019-05-03T21:12:09Z 2019-05-03T21:11:20Z CONTRIBUTOR simonw/datasette/pulls/367

GitHub lists datasette as a Javascript project, primarily because of the vendored codemirror files. This is somewhat confusing when you're looking for datasette, knowing it's written in Python.

Luckily it's possible exclude certain files from GitHub's code statistics: https://github.com/github/linguist#using-gitattributes

 datasette 107914493 pull     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/367/reactions",
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 0  
374676773 MDExOlB1bGxSZXF1ZXN0MjI2MzE1NTEz 368 Update installation instructions jaap3 48517 closed 0     0 2018-10-27T18:52:31Z 2019-05-03T18:18:43Z 2019-05-03T18:18:42Z CONTRIBUTOR simonw/datasette/pulls/368

I was writing this as a response to your tweet, but decided I might just make it a pull request.

I feel like it might be confusing to those unfamiliar with Python's -m flag and the built-in venv module to omit the space between the flag and its argument. By adding a space and prefixing the second occurrence of venv with a ./ it's maybe a bit clearer what the arguments are and what they do.

By also using python3 -m pip it becomes even clearer that -m is a special flag that makes the python executable do neat things.

 datasette 107914493 pull     
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/368/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 0  

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