issues

Table actions

4 rows where user = 3234522 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

type 1

state 1

repo 1

id node_id number title user state locked assignee milestone comments created_at updated_at ▲ closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
1996567640 PR_kwDOAMm_X85fnTeD 8457 Fix typos found by codespell DimitriPapadopoulos 3234522 closed 0     1 2023-11-16T10:41:45Z 2023-11-16T17:02:55Z 2023-11-16T15:29:54Z CONTRIBUTOR   0 pydata/xarray/pulls/8457   
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/8457/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
1962379547 PR_kwDOAMm_X85dzj5A 8375 Fix typos found by codespell DimitriPapadopoulos 3234522 closed 0     3 2023-10-25T22:37:45Z 2023-10-26T18:17:38Z 2023-10-26T17:26:59Z CONTRIBUTOR   0 pydata/xarray/pulls/8375
  • [ ] Closes #xxxx
  • [ ] Tests added
  • [ ] User visible changes (including notable bug fixes) are documented in whats-new.rst
  • [ ] New functions/methods are listed in api.rst
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/8375/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
1963084121 PR_kwDOAMm_X85d17_p 8379 Do not intercept left/right keys in HTML docs DimitriPapadopoulos 3234522 closed 0     1 2023-10-26T09:22:58Z 2023-10-26T14:26:36Z 2023-10-26T14:00:01Z CONTRIBUTOR   0 pydata/xarray/pulls/8379

This will be the default in upcoming versions of Sphinx, but let's proactively and explicitly set to False, instead of the current and implicit True. See warning in https://github.com/pydata/xarray/pull/8375#issuecomment-1780716514.

See: https://github.com/pydata/pydata-sphinx-theme/issues/1492

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/8379/reactions",
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
1306850342 PR_kwDOAMm_X847g0cj 6794 Fix typos found by codespell DimitriPapadopoulos 3234522 closed 0     1 2022-07-16T16:35:51Z 2022-07-18T13:04:46Z 2022-07-16T17:02:55Z CONTRIBUTOR   0 pydata/xarray/pulls/6794

The inferrable → inferable change is debatable, but the most common spelling does appear to be the latter (Google hits support that): * Merriam-Webster * Collins * Wiktionary * Lexico

  • [ ] Closes #xxxx
  • [ ] Tests added
  • [ ] User visible changes (including notable bug fixes) are documented in whats-new.rst
  • [ ] New functions/methods are listed in api.rst
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/6794/reactions",
    "total_count": 2,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 2,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull

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,
   [active_lock_reason] TEXT,
   [draft] INTEGER,
   [pull_request] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [state_reason] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] 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]);