issue_comments

Table actions

3 rows where author_association = "MEMBER", issue = 773934304 and user = 13301940 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • andersy005 · 3 ✖

issue 1

  • Trigger upstream CI on cron schedule (by default) · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
755750876 https://github.com/pydata/xarray/pull/4729#issuecomment-755750876 https://api.github.com/repos/pydata/xarray/issues/4729 MDEyOklzc3VlQ29tbWVudDc1NTc1MDg3Ng== andersy005 13301940 2021-01-06T22:16:54Z 2021-01-06T22:16:54Z MEMBER

Thank you for input and feedback @keewis and @dcherian 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Trigger upstream CI on cron schedule (by default) 773934304
753718540 https://github.com/pydata/xarray/pull/4729#issuecomment-753718540 https://api.github.com/repos/pydata/xarray/issues/4729 MDEyOklzc3VlQ29tbWVudDc1MzcxODU0MA== andersy005 13301940 2021-01-04T01:56:56Z 2021-01-04T01:56:56Z MEMBER

this currently does not work because actions/checkout seems to checkout some merge commit it creates. Any idea how to fix that, @andersy005?

Interesting... I am looking into it and will get back to you once I figure something out... 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Trigger upstream CI on cron schedule (by default) 773934304
750393141 https://github.com/pydata/xarray/pull/4729#issuecomment-750393141 https://api.github.com/repos/pydata/xarray/issues/4729 MDEyOklzc3VlQ29tbWVudDc1MDM5MzE0MQ== andersy005 13301940 2020-12-23T17:12:06Z 2020-12-23T17:12:06Z MEMBER

I think there were a few tricks we used to make sure certain steps are only run for the scheduled CI. Should we remove them now,

I just removed them (without the other event types, we don't need them anymore). I am going to submit another PR with the migration of the other CI to GitHub actions. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Trigger upstream CI on cron schedule (by default) 773934304

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