issue_comments
6 rows where issue = 870292042 and user = 13301940 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- release v0.18.0 · 6 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
833782283 | https://github.com/pydata/xarray/issues/5232#issuecomment-833782283 | https://api.github.com/repos/pydata/xarray/issues/5232 | MDEyOklzc3VlQ29tbWVudDgzMzc4MjI4Mw== | andersy005 13301940 | 2021-05-06T18:59:01Z | 2021-05-06T18:59:01Z | MEMBER |
Or we could just set
on the upload to TestPyPI step. |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
release v0.18.0 870292042 | |
833774532 | https://github.com/pydata/xarray/issues/5232#issuecomment-833774532 | https://api.github.com/repos/pydata/xarray/issues/5232 | MDEyOklzc3VlQ29tbWVudDgzMzc3NDUzMg== | andersy005 13301940 | 2021-05-06T18:50:11Z | 2021-05-06T18:50:46Z | MEMBER | @keewis, do we need to do anything with the release on test.pypi.org? (since the v0.18 is already published there) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
release v0.18.0 870292042 | |
833772828 | https://github.com/pydata/xarray/issues/5232#issuecomment-833772828 | https://api.github.com/repos/pydata/xarray/issues/5232 | MDEyOklzc3VlQ29tbWVudDgzMzc3MjgyOA== | andersy005 13301940 | 2021-05-06T18:48:41Z | 2021-05-06T18:48:41Z | MEMBER |
Yes... |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
release v0.18.0 870292042 | |
833768930 | https://github.com/pydata/xarray/issues/5232#issuecomment-833768930 | https://api.github.com/repos/pydata/xarray/issues/5232 | MDEyOklzc3VlQ29tbWVudDgzMzc2ODkzMA== | andersy005 13301940 | 2021-05-06T18:43:04Z | 2021-05-06T18:43:04Z | MEMBER | I accidentally closed this via Github's keywords... The bug in the CI workflow should be fixed. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
release v0.18.0 870292042 | |
833753256 | https://github.com/pydata/xarray/issues/5232#issuecomment-833753256 | https://api.github.com/repos/pydata/xarray/issues/5232 | MDEyOklzc3VlQ29tbWVudDgzMzc1MzI1Ng== | andersy005 13301940 | 2021-05-06T18:19:41Z | 2021-05-06T18:19:41Z | MEMBER | Never mind... There's a bug in this It should be |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
release v0.18.0 870292042 | |
833741743 | https://github.com/pydata/xarray/issues/5232#issuecomment-833741743 | https://api.github.com/repos/pydata/xarray/issues/5232 | MDEyOklzc3VlQ29tbWVudDgzMzc0MTc0Mw== | andersy005 13301940 | 2021-05-06T18:03:01Z | 2021-05-06T18:03:13Z | MEMBER |
Sorry about that. I think the culprit here are the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
release v0.18.0 870292042 |
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