issue_comments
2 rows where author_association = "MEMBER", issue = 833778859 and user = 14808389 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Allow assigning values to a subset of a dataset · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 832902960 | https://github.com/pydata/xarray/pull/5045#issuecomment-832902960 | https://api.github.com/repos/pydata/xarray/issues/5045 | MDEyOklzc3VlQ29tbWVudDgzMjkwMjk2MA== | keewis 14808389 | 2021-05-05T18:13:22Z | 2021-05-05T18:13:22Z | MEMBER | could you also resolve the merge conflicts? It seems we can't "approve and run" the CI with conflicts. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Allow assigning values to a subset of a dataset 833778859 | |
| 822337622 | https://github.com/pydata/xarray/pull/5045#issuecomment-822337622 | https://api.github.com/repos/pydata/xarray/issues/5045 | MDEyOklzc3VlQ29tbWVudDgyMjMzNzYyMg== | keewis 14808389 | 2021-04-19T09:52:45Z | 2021-04-19T09:52:45Z | MEMBER | that's a flaky test which randomly fails (see #4539). You can safely ignore it, the CI should pass on the next run. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Allow assigning values to a subset of a dataset 833778859 |
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