issues: 994264727
This data as json
| id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 994264727 | MDExOlB1bGxSZXF1ZXN0NzMyMjM5NjEw | 5787 | Update issue template to include a checklist | 5635139 | closed | 0 | 7 | 2021-09-12T19:47:23Z | 2022-04-27T08:23:27Z | 2022-04-27T00:56:27Z | MEMBER | 0 | pydata/xarray/pulls/5787 | This may be overly prescriptive. We've had a number of recent issues which aren't minimal and link to external data, and then these languish on the Issue Tracker unanswered. That's a loss of time for all involved — the reporter of the issue as well as the maintainers. To the extent we can predict which issues will languish, it would be better to give that guidance up front, and encourage examples which are easier to engage with. So this introduces a checklist that people need to proactively fill out. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/5787/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
13221727 | pull |