issue_comments

Table actions

5 rows where issue = 784628736 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

issue 1

  • scheduled upstream-dev CI is skipped · 5 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
759749910 https://github.com/pydata/xarray/issues/4801#issuecomment-759749910 https://api.github.com/repos/pydata/xarray/issues/4801 MDEyOklzc3VlQ29tbWVudDc1OTc0OTkxMA== keewis 14808389 2021-01-13T21:27:08Z 2021-01-14T00:09:43Z MEMBER

I'm currently experimenting in #4805, but maybe we have to be smarter about how many commits to fetch.

Edit: ~it seems that this only fails for merge commits.~ that's wrong, I don't know why it fails

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   scheduled upstream-dev CI is skipped 784628736
759749060 https://github.com/pydata/xarray/issues/4801#issuecomment-759749060 https://api.github.com/repos/pydata/xarray/issues/4801 MDEyOklzc3VlQ29tbWVudDc1OTc0OTA2MA== andersy005 13301940 2021-01-13T21:25:25Z 2021-01-13T21:25:25Z MEMBER

the trigger also seems to be broken: the action fails because HEAD^2 apparently is not always a valid ref for pull request events.

Do you have any thoughts on how to address this?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   scheduled upstream-dev CI is skipped 784628736
759748428 https://github.com/pydata/xarray/issues/4801#issuecomment-759748428 https://api.github.com/repos/pydata/xarray/issues/4801 MDEyOklzc3VlQ29tbWVudDc1OTc0ODQyOA== keewis 14808389 2021-01-13T21:24:06Z 2021-01-13T21:24:06Z MEMBER

Oh, thanks, that makes sense. I'll send in a PR.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   scheduled upstream-dev CI is skipped 784628736
759747669 https://github.com/pydata/xarray/issues/4801#issuecomment-759747669 https://api.github.com/repos/pydata/xarray/issues/4801 MDEyOklzc3VlQ29tbWVudDc1OTc0NzY2OQ== andersy005 13301940 2021-01-13T21:22:36Z 2021-01-13T21:22:36Z MEMBER

@keewis, I think the issue has to do with a typo in this condition:

https://github.com/pydata/xarray/blob/fb67358ceb0c386560e6a6991dd937292ba54d46/.github/workflows/upstream-dev-ci.yaml#L35

The right event name is schedule instead of scheduled: github.event_name == 'scheduled' --> github.event_name == 'schedule'

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   scheduled upstream-dev CI is skipped 784628736
759741037 https://github.com/pydata/xarray/issues/4801#issuecomment-759741037 https://api.github.com/repos/pydata/xarray/issues/4801 MDEyOklzc3VlQ29tbWVudDc1OTc0MTAzNw== keewis 14808389 2021-01-13T21:09:15Z 2021-01-13T21:09:15Z MEMBER

the trigger also seems to be broken: the action fails because HEAD^2 apparently is not always a valid ref for pull request events.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   scheduled upstream-dev CI is skipped 784628736

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]);