pull_requests

Table actions

3 rows where user = 6200806

✖
✖

✎ 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 auto_merge repo url merged_by
57757338 MDExOlB1bGxSZXF1ZXN0NTc3NTczMzg= 736 closed 0 Accept rename to same name spencerahill 6200806 Closes #724 2016-01-31T02:17:01Z 2016-02-02T03:44:33Z 2016-02-02T01:33:03Z 2016-02-02T01:33:03Z 05ad93aaa50741f8e0c8c93b4eb7aeafba92650b     0 7fec195dbb6ad000cd04a22c39641f9e4edd5d30 c102a4095b4575a9d7d355fb4ddbc8e684d16fb8 CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/736  
102205437 MDExOlB1bGxSZXF1ZXN0MTAyMjA1NDM3 1219 closed 0 ENH import ufuncs module in toplevel namespace spencerahill 6200806 - [x] closes #1216 - [ ] tests added / passed - [ ] passes ``git diff upstream/master | flake8 --diff`` - [ ] whatsnew entry Let me know if you want tests and/or what's new; wasn't sure since this is so small. 2017-01-19T05:51:02Z 2017-02-07T04:40:16Z 2017-01-19T05:59:26Z 2017-01-19T05:59:26Z b44b37a5bd8fb613e6a7ce9c82c91e31b7ddf9bc     0 0173a35dcd951e7afce7ac3a1c3ac21463240cd2 e98ea103647ba72e758b77797ece9896055ddc77 CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/1219  
395017613 MDExOlB1bGxSZXF1ZXN0Mzk1MDE3NjEz 3906 closed 0 Fix for stack+groupby+apply w/ non-increasing coord spencerahill 6200806 <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Fixes #3287 - [x] Tests added - [x] Passes `isort -rc . && black . && mypy . && flake8` - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API I've added a check within `groupby.__init__` for monotonicity of the coords, which makes my test pass, but it causes three existing tests to fail. Getting the logic right that properly distinguishes among these different cases is escaping me for now, but it does seem like this call to `unique_value_groups` within `groupby.__init__` is where the re-sorting is occurring. Feedback welcome. TIA! 2020-03-28T00:15:20Z 2020-03-31T18:29:35Z 2020-03-31T16:10:10Z 2020-03-31T16:10:09Z b3bafeefbd6e6d70bce505ae1f0d9d5a2b015089     0 24b3752cd07d823b83abaa93ad12502906da7fc7 eb8e43b717651cdbf65b09226d97661ce60ba446 CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/3906  

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,
   [auto_merge] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [url] TEXT,
   [merged_by] INTEGER REFERENCES [users]([id])
);
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]);