issue_comments

Table actions

1 row where issue = 1615645463 and user = 43316012 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • headtr1ck · 1 ✖

issue 1

  • Fix missing 'dim' argument in _get_nan_block_lengths · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1460859161 https://github.com/pydata/xarray/pull/7598#issuecomment-1460859161 https://api.github.com/repos/pydata/xarray/issues/7598 IC_kwDOAMm_X85XEvEZ headtr1ck 43316012 2023-03-08T20:50:46Z 2023-03-08T20:50:46Z COLLABORATOR

As a newcomer, a short general question: The 'Contributing' guide mentions to document changes in whats-new.rst. Shall this be done by the developer or are you (the maintainers) doing this once the PR is merged into the main branch?

(Since at the time of requesting, I can`t know when (or if) the issue will be merged).

Usually this is done by the developer/contributor. You can just copy a similar entry and adopt it to yourself in the newest section, you have basically full freedom :)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix missing 'dim' argument in _get_nan_block_lengths 1615645463

Advanced export

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

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);