Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify close as not planned for triage #1186

Merged
merged 1 commit into from
Oct 11, 2023
Merged

Conversation

willingc
Copy link
Collaborator

@willingc willingc commented Oct 11, 2023

Clarify the close step in the triage checklist. TIL from @erlend-aasland. 👍🏼


📚 Documentation preview 📚: https://cpython-devguide--1186.org.readthedocs.build/

@hugovk hugovk merged commit 941598d into python:main Oct 11, 2023
3 checks passed
@willingc willingc deleted the close-option branch October 11, 2023 14:47
@zware
Copy link
Member

zware commented Oct 11, 2023

If there's a canonical link to GitHub documentation about how to use that option, it might be a good idea to link the new text to it. I've seen several people not realize that the dropdown on the close button offered options (or even existed).

@AlexWaygood
Copy link
Member

If there's a canonical link to GitHub documentation about how to use that option, it might be a good idea to link the new text to it. I've seen several people not realize that the dropdown on the close button offered options (or even existed).

There's some docs here that provide a screenshot: https://docs.github.com/en/issues/tracking-your-work-with-issues/closing-an-issue

Though actually, the blog post here announcing the feature is even better: https://github.blog/changelog/2022-03-10-the-new-github-issues-march-10th-update/#🕵🏽♀%EF%B8%8F-issue-closed-reasons

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants