issue_comments

Table actions

3 rows where author_association = "MEMBER", issue = 994264727 and user = 5635139 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 1

  • max-sixty · 3 ✖

issue 1

  • Update issue template to include a checklist · 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
1110385272 https://github.com/pydata/xarray/pull/5787#issuecomment-1110385272 https://api.github.com/repos/pydata/xarray/issues/5787 IC_kwDOAMm_X85CLyJ4 max-sixty 5635139 2022-04-27T00:43:05Z 2022-04-27T08:23:27Z MEMBER

@pydata/xarray

I've refreshed this, since I've been spending time in the issue tracker recently and would like to systematize myself out of the "please add an MVCE" triagooor.

I also added a empty binder notebook & link, so people can easily test against a current version of dependencies. I've been using this myself given my M1 has been prickly for some xarray dependencies. Binder is great.

I'd be up for making it more friendly, if possible. But I do think we should be strict on issue quality. Some claims: - Most people want to[^1] invest the time to make good issues, and the existing outcomes are mostly a gap of direction & nudging - An unanswered issue (of which we have many, unfortunately) is worse than no issue at all — people feel that there's no prospect of a resolution to their concerns - Bad issues take time away from good issues, and lower maintainers' willingness to spend time in the issue tracker - Friendliness is a virtue. It's difficult to be friendly when managing bad issues, it's very easy when dealing with good issues

[^1]: or at least are not adverse to :)

This is the current draft:

And the checkboxes:

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Update issue template to include a checklist 994264727
1110693353 https://github.com/pydata/xarray/pull/5787#issuecomment-1110693353 https://api.github.com/repos/pydata/xarray/issues/5787 IC_kwDOAMm_X85CM9Xp max-sixty 5635139 2022-04-27T08:15:37Z 2022-04-27T08:15:37Z MEMBER

Sorry, thanks for letting me know, that was a mistake. I'll restore.

I've had some issues with my github scripts today...

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Update issue template to include a checklist 994264727
1007241910 https://github.com/pydata/xarray/pull/5787#issuecomment-1007241910 https://api.github.com/repos/pydata/xarray/issues/5787 IC_kwDOAMm_X848CUq2 max-sixty 5635139 2022-01-07T08:59:32Z 2022-01-07T08:59:32Z MEMBER

Not quite; since this given a specific checklist that people need to complete. Sorry I let this linger. I can finish soon-ish.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Update issue template to include a checklist 994264727

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