pull_requests

Table actions

3 rows where user = 296686

✎ 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
83007736 MDExOlB1bGxSZXF1ZXN0ODMwMDc3MzY= 990 closed 0 Added convenience method for saving DataArray to netCDF file robintw 296686 Added a simple function to DataArray that creates a dataset with one variable called 'data' and then saves it to a netCDF file. All parameters are passed through to to_netcdf(). Added an equivalent function called `open_dataarray` to be used to load from these files. Fixes #915. 2016-08-28T06:30:32Z 2016-09-06T04:00:25Z 2016-09-06T04:00:06Z 2016-09-06T04:00:06Z 69ac5117f536836a0fa75ad17779f818b4f8ee28     0 4920def809716c4ebfce930f56f06e047c9917d3 c80aa82ad8b4116f742738c2cf2dac1cdd5c8f4e CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/990  
83012431 MDExOlB1bGxSZXF1ZXN0ODMwMTI0MzE= 991 closed 0 Added validation of attrs before saving to netCDF files robintw 296686 This allows us to give nice errors if users try to save a Dataset with attr values that can't be written to a netCDF file. Fixes #911. I've added tests to `test_backends.py` as I can't see a better place to put them. I've also made the tests fairly extensive, but also used some helper functions to stop too much repetition. Please let me know if any of this doesn't fit within the xarray style. 2016-08-28T11:01:18Z 2016-09-02T22:52:09Z 2016-09-02T22:52:04Z 2016-09-02T22:52:04Z c80aa82ad8b4116f742738c2cf2dac1cdd5c8f4e     0 ce3bf5458c52669713b00161943ea5ca6bbd452f 8a87c3545dd42b4c8032f1b0fbf87b84e5d7f793 CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/991  
206807293 MDExOlB1bGxSZXF1ZXN0MjA2ODA3Mjkz 2351 closed 0 Remove redundant code from open_rasterio and ensure all transform tuples are six elements long robintw 296686 - [x] Closes #2348 - [x] Tests added (for all bug fixes or enhancements) - [x] Tests passed (for all non-documentation changes) - [ ] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API (remove if this change should not be visible to users, e.g., if it is an internal clean-up, or if this is part of a larger project that will be documented later) This removes the redundant code that ended up with the `transform` attribute being set twice - and being set to a nine-element long tuple rather than the correct six-element long tuple. It also adds tests to ensure that all `transform` attributes are six-element-long tuples. I haven't made any changes to the documentation, as I wasn't sure if it was needed. This could potentially affect users as the documentation and the code differed and people may have written other interface code (as, in my case, code to export a DataArray to a GeoTIFF using rasterio) which relies on the transform element having 9 elements rather than the 6 it is meant to have. Any thoughts? 2018-08-07T19:48:39Z 2018-08-13T22:34:18Z 2018-08-13T22:33:54Z 2018-08-13T22:33:54Z 4df048c146b8da7093faf96b3e59fb4d56945ec5     0 0cc248853877feceff70506e39cb8f3228684b12 0a60a52521e41dce897e265ac549cbf88c670faa CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/2351  

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