issue_comments
2 rows where issue = 1030492705 and user = 14371165 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- _season_from_months can now handle np.nan · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
949270052 | https://github.com/pydata/xarray/pull/5876#issuecomment-949270052 | https://api.github.com/repos/pydata/xarray/issues/5876 | IC_kwDOAMm_X844lLYk | Illviljan 14371165 | 2021-10-22T04:08:59Z | 2021-10-22T04:08:59Z | MEMBER | The code linting errors are still there and needs to be fixed, you can copy those changes to get that check passing. We use |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
_season_from_months can now handle np.nan 1030492705 | |
948893303 | https://github.com/pydata/xarray/pull/5876#issuecomment-948893303 | https://api.github.com/repos/pydata/xarray/issues/5876 | IC_kwDOAMm_X844jvZ3 | Illviljan 14371165 | 2021-10-21T18:29:44Z | 2021-10-21T18:29:44Z | MEMBER |
But there's a few code linting errors which pep8speaks is also complaining about. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
_season_from_months can now handle np.nan 1030492705 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 1