issue_comments

Table actions

2 rows where author_association = "MEMBER" and issue = 673682661 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

issue 1

  • Using Dependabot to manage doc build and CI versions · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
669545482 https://github.com/pydata/xarray/issues/4313#issuecomment-669545482 https://api.github.com/repos/pydata/xarray/issues/4313 MDEyOklzc3VlQ29tbWVudDY2OTU0NTQ4Mg== shoyer 1217238 2020-08-05T22:06:42Z 2020-08-05T22:06:42Z MEMBER

The other question is if dependabot can be configured to update a subset of specific requirements.txt files?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Using Dependabot to manage doc build and CI versions 673682661
669544335 https://github.com/pydata/xarray/issues/4313#issuecomment-669544335 https://api.github.com/repos/pydata/xarray/issues/4313 MDEyOklzc3VlQ29tbWVudDY2OTU0NDMzNQ== shoyer 1217238 2020-08-05T22:03:40Z 2020-08-05T22:03:40Z MEMBER

This does seem like it would be really nice for us!

The main limitation compared to our current setup is that we currently ping dependencies using Conda's yml files, e.g., https://github.com/pydata/xarray/blob/master/ci/requirements/py36.yml

But it sounds like conda can use requirements.txt files, too, these days? In which case this is just a matter of migration.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Using Dependabot to manage doc build and CI versions 673682661

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