pull_requests

Table actions

2 rows where user = 56583917

✎ 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
1702397358 PR_kwDOAMm_X85leIWu 8683 closed 0 Docs: Fix url in "Contribute to xarray" guide maawoo 56583917 The URL in the section about [creating a local development environment](https://docs.xarray.dev/en/stable/contributing.html#creating-a-development-environment) was pointing to itself. The new URL is pointing to the (I assume) correct section further down in the same guide. 2024-01-30T15:59:37Z 2024-01-30T18:13:36Z 2024-01-30T18:13:26Z 2024-01-30T18:13:26Z 614c25b165c18458570f5a68e03034f9b87cf1e7     0 e9574c886a0a5021f6ab22033574f97adec0e694 81f38f3de4260561ddc89f82981a0d6daa6cede6 CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/8683  
1702704223 PR_kwDOAMm_X85lfTRf 8684 closed 0 Enable `numbagg` in calculation of quantiles maawoo 56583917 <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Closes #7377 - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` Just saw your message in the related issue @max-sixty. This is what I came up with earlier. I also did a quick test, comparing the calculation with and without using numbagg for a dummy 3D DataArray. I was only wondering if the default usage of numbagg (given that it's available and `method='linear'`) should be noted somewhere in the docstrings and/or the docs in general. 2024-01-30T18:59:55Z 2024-02-11T22:31:26Z 2024-02-07T16:28:04Z 2024-02-07T16:28:04Z 0eb66587c44411abc668e96881a51e1b99e1eb9e     0 18ef827afd0f4b35a014ab987ca559eddece98bb f33a632bf87ec29dd9346f9b01ad4eec2194f72a CONTRIBUTOR   xarray 13221727 https://github.com/pydata/xarray/pull/8684  

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