issue_comments

Table actions

2 rows where author_association = "CONTRIBUTOR", issue = 484711431 and user = 221526 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

  • dopplershift · 2 ✖

issue 1

  • 0.13.0 release · 2 ✖

author_association 1

  • CONTRIBUTOR · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
525441141 https://github.com/pydata/xarray/issues/3257#issuecomment-525441141 https://api.github.com/repos/pydata/xarray/issues/3257 MDEyOklzc3VlQ29tbWVudDUyNTQ0MTE0MQ== dopplershift 221526 2019-08-27T19:06:42Z 2019-08-27T19:06:42Z CONTRIBUTOR

On Travis I have some deploy hooks: 1. Using Travis' built-in PyPI support, it uploads wheels and sdist, only on tags 2. Execute a custom script to commit built docs to github pages (not RTD). On master builds, this updates dev docs. On a tag, it adds a new directory for that version of the docs.

Travis Config Doc Deploy Script

 
{
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 1,
    "rocket": 0,
    "eyes": 0
}
   0.13.0 release 484711431
525405541 https://github.com/pydata/xarray/issues/3257#issuecomment-525405541 https://api.github.com/repos/pydata/xarray/issues/3257 MDEyOklzc3VlQ29tbWVudDUyNTQwNTU0MQ== dopplershift 221526 2019-08-27T17:34:55Z 2019-08-27T17:34:55Z CONTRIBUTOR

The benefit to automation also makes it easier to distribute the workload to other people, helping with project sustainability. On my projects, I find it very nice that I make a new release on GitHub and packages appear on PyPI and the web docs are automatically updated to the new version.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   0.13.0 release 484711431

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