pull_requests

Table actions

3 rows where user = 418191

✎ View and edit SQL

This data as json, CSV (advanced)

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

id ▼ node_id number state locked title user body created_at updated_at closed_at merged_at merge_commit_sha assignee milestone draft head base author_association repo url merged_by auto_merge
216651317 MDExOlB1bGxSZXF1ZXN0MjE2NjUxMzE3 365 closed 0 fix small doc typo jaywgraves 418191   2018-09-19T14:02:02Z 2019-12-19T02:30:33Z 2018-09-19T17:15:43Z 2018-09-19T17:15:43Z 1bcd54a834a2f9730d21095df855f6708c85c200     0 d3fb6a80c5878c73befa2a35e11a9ce28a6e1ab6 b7257a21bf3dfa7353980f343c83a616da44daa7 CONTRIBUTOR datasette 107914493 https://github.com/simonw/datasette/pull/365    
235194286 MDExOlB1bGxSZXF1ZXN0MjM1MTk0Mjg2 390 closed 0 tiny typo in customization docs jaywgraves 418191 was looking to add some custom templates to my use of datasette and saw this small typo. 2018-12-01T13:44:42Z 2019-12-19T02:30:35Z 2018-12-16T21:32:56Z 2018-12-16T21:32:56Z ed78922ae38b51513319b60ac39990b7c2aca810     0 f8c01373dad3b8dcd10577a2e541f88ef34c77bc 3de8fac1d322cbab6c8c55899e0e8511b36337d0 CONTRIBUTOR datasette 107914493 https://github.com/simonw/datasette/pull/390    
356004242 MDExOlB1bGxSZXF1ZXN0MzU2MDA0MjQy 653 closed 0 allow leading comments in SQL input field jaywgraves 418191 this changes the SQL validation to allow for lines that are commented out my main use case for this is that I like to write a succession of queries when trying to solve a problem. In most native SQL clients there is a key binding that will run just the current highlighted query or the program is smart enough to run just the query that the cursor is in if it's properly delimited with a ';'. Typically my workflow will start with a single simple query and I'll copy/paste it to a new query below when I want to make big changes while debugging. This makes it easy to go back to a working version above when the query doesn't work. Since datasette sends the whole query to the DB I have to comment out the older queries by prefixing each line with `--`. This gets caught by the validators when I use my typical strategy of copy/pasting each successive query below the last one. so this is just a simple fix to allow for a query to be sent to the DB with leading comments. 2019-12-21T14:19:52Z 2020-02-05T02:35:41Z 2020-02-05T02:13:25Z 2020-02-05T02:13:25Z 33a12c8ae526afb40a7819c9ca411c9d3c41219b     0 3a4cb551b9a217d5798e3e9ad5d4b06234a81885 d6b6c9171f3fd945c4e5e4144923ac831c43c208 CONTRIBUTOR datasette 107914493 https://github.com/simonw/datasette/pull/653    

Advanced export

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

CSV options: 

CREATE TABLE [pull_requests] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [state] TEXT,
   [locked] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [body] TEXT,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [merged_at] TEXT,
   [merge_commit_sha] TEXT,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [draft] INTEGER,
   [head] TEXT,
   [base] TEXT,
   [author_association] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [url] TEXT,
   [merged_by] INTEGER REFERENCES [users]([id])
, [auto_merge] TEXT);
CREATE INDEX [idx_pull_requests_merged_by]
    ON [pull_requests] ([merged_by]);
CREATE INDEX [idx_pull_requests_repo]
    ON [pull_requests] ([repo]);
CREATE INDEX [idx_pull_requests_milestone]
    ON [pull_requests] ([milestone]);
CREATE INDEX [idx_pull_requests_assignee]
    ON [pull_requests] ([assignee]);
CREATE INDEX [idx_pull_requests_user]
    ON [pull_requests] ([user]);