issue_comments

Table actions

3 rows where issue = 1221918339 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

  • Remove duplicate tests, v3 · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1114071096 https://github.com/pydata/xarray/pull/6550#issuecomment-1114071096 https://api.github.com/repos/pydata/xarray/issues/6550 IC_kwDOAMm_X85CZ2A4 keewis 14808389 2022-04-30T23:22:22Z 2022-04-30T23:22:22Z MEMBER

the duplication will only happen for branches on the main repository, forks will not see this.

As far as I can tell that's what #5142 added, which we removed when we switched to github's concurrency feature. Not sure if concurrency has a setting for that? Otherwise we might have to add back that step

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Remove duplicate tests, v3 1221918339
1114070386 https://github.com/pydata/xarray/pull/6550#issuecomment-1114070386 https://api.github.com/repos/pydata/xarray/issues/6550 IC_kwDOAMm_X85CZ11y max-sixty 5635139 2022-04-30T23:15:44Z 2022-04-30T23:15:44Z MEMBER

Yes I'm not sure — does having push for all branches and and pull_request for all branches cause duplicates?

(Not a huge deal since we're using this fork to push branches; this only happened because I hit the revert button on GH)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Remove duplicate tests, v3 1221918339
1114069037 https://github.com/pydata/xarray/pull/6550#issuecomment-1114069037 https://api.github.com/repos/pydata/xarray/issues/6550 IC_kwDOAMm_X85CZ1gt keewis 14808389 2022-04-30T23:07:12Z 2022-04-30T23:07:12Z MEMBER

duplicating all the tests

that's strange, I thought we disabled that? What did we change that broke the "either pull_request or push" filter?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Remove duplicate tests, v3 1221918339

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