issue_comments
2 rows where issue = 916318941 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Add coarsen.construct · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 857834962 | https://github.com/pydata/xarray/issues/5454#issuecomment-857834962 | https://api.github.com/repos/pydata/xarray/issues/5454 | MDEyOklzc3VlQ29tbWVudDg1NzgzNDk2Mg== | dcherian 2448579 | 2021-06-09T16:07:13Z | 2021-06-09T16:07:13Z | MEMBER |
We could incorporate the renaming like this. Thoughts?
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Add coarsen.construct 916318941 | |
| 857818850 | https://github.com/pydata/xarray/issues/5454#issuecomment-857818850 | https://api.github.com/repos/pydata/xarray/issues/5454 | MDEyOklzc3VlQ29tbWVudDg1NzgxODg1MA== | shoyer 1217238 | 2021-06-09T15:46:06Z | 2021-06-09T15:46:06Z | MEMBER | Yes, we should totally do this! This is a very common operation in machine learning workflows, e.g., in TensorFlow it's |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Add coarsen.construct 916318941 |
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 2