Promote usage of close reasons #870
Labels
Comments
|
There is no need to resolve this until the triage section has been rewritten with regards to the new GitHub Issues workflow. |
za
added a commit
to za/devguide
that referenced
this issue
Jun 2, 2022
where now we can opt to close as complete or not-planned. GH issue: python#870 GH blog: https://github.blog/changelog/2022-05-19-the-new-github-issues-may-19th-update/
ezio-melotti
pushed a commit
that referenced
this issue
Jun 5, 2022
* Added Closing PR section where now we can opt to close as complete or not-planned. GH issue: #870 GH blog: https://github.blog/changelog/2022-05-19-the-new-github-issues-may-19th-update/ * Remove new section and remove github blog hyperlink. * Modify tracker.rst and restore pullrequest.rst because the closed reason is for issues and not for pull request.
|
As the PR has been merged, can we close/resolve this issue now @ezio-melotti ? |
|
Thanks @ezio-melotti I'll add keyword in the next PR so once PR has been merged, the issue will automatically closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
GitHub released new features for issues today: https://github.blog/changelog/2022-05-19-the-new-github-issues-may-19th-update/
It is now possible to close as completed, or close as not planned (won't fix, no repro, invalid, etc.). It is possible to filter searches using
reason:completedandreason:"not planned".Suggesting to promote usage of closing reasons in the devguide.
The text was updated successfully, but these errors were encountered: