From ddd3b3862f6afc2d362df59e1499a88d0927aab4 Mon Sep 17 00:00:00 2001 From: Sophie <29382425+sophietheking@users.noreply.github.com> Date: Wed, 15 Mar 2023 08:32:12 +0100 Subject: [PATCH] [2023-03-14]: Ability to close Discussions (GA) (#35397) Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com> --- .../about-discussions.md | 2 +- .../managing-discussions.md | 13 +++++++++++++ .../moderating-discussions.md | 8 ++++++++ data/features/discussions-closable.yml | 6 ++++++ data/reusables/discussions/closing-discussions.md | 1 + 5 files changed, 29 insertions(+), 1 deletion(-) create mode 100644 data/features/discussions-closable.yml create mode 100644 data/reusables/discussions/closing-discussions.md diff --git a/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md index 65c704ebb3..ff4dba80cb 100644 --- a/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md +++ b/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -20,7 +20,7 @@ With {% data variables.product.prodname_discussions %}, the community for your p You might use repository discussions to discuss topics that are specific to the repository. If your project spans multiple repositories, you might use organization discussions to discuss topics that aren't specific to a single repository in your organization. -You don't need to close a discussion like you close an issue or a pull request. +{% ifversion discussions-closable %}{% data reusables.discussions.closing-discussions %} For more information, see "[Closing a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#closing-a-discussion)."{% else %}You don't need to close a discussion like you close an issue or a pull request.{% endif %} If a repository administrator or project maintainer enables {% data variables.product.prodname_discussions %} for a repository, anyone who has access to the repository can create and participate in discussions for the repository. If an organization owner enables {% data variables.product.prodname_discussions %} for an organization, anyone who can view the source repository can create an organization discussion. diff --git a/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/content/discussions/managing-discussions-for-your-community/managing-discussions.md index 12afff7af6..2a253b0ec8 100644 --- a/content/discussions/managing-discussions-for-your-community/managing-discussions.md +++ b/content/discussions/managing-discussions-for-your-community/managing-discussions.md @@ -165,6 +165,19 @@ To transfer a discussion, you must have permissions to create discussions in the 1. Read the warning, then click **Delete this discussion**. +{% ifversion discussions-closable %} +## Closing a discussion + +{% data reusables.discussions.closing-discussions %} + +{% data reusables.discussions.navigate-to-repo-or-org %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. At the bottom of the discussion, below the comment box, click **Close discussion**. +1. Optionally, to change the reason for closing the discussion, select the {% octicon "triangle-down" aria-label="The down triangle octicon" %} dropdown next to "Close discussion" and click a reason. + +{% endif %} + ## Converting issues based on labels You can convert all issues with the same label to discussions in bulk. Future issues with this label will also automatically convert to the discussion and category you configure. diff --git a/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/content/discussions/managing-discussions-for-your-community/moderating-discussions.md index 07c935a344..8d941ea553 100644 --- a/content/discussions/managing-discussions-for-your-community/moderating-discussions.md +++ b/content/discussions/managing-discussions-for-your-community/moderating-discussions.md @@ -19,6 +19,14 @@ versions: It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/free-pro-team@latest/site-policy/github-terms/github-community-guidelines). You can also lock a conversation to prevent comments on a discussion you want to use as an announcement to the community. When you lock a conversation, people with write access to the repository, or source repository for organization discussions, will still be able to comment on the discussion. {% ifversion discussions-lock-allow-reactions %}You can also allow emoji reactions to a locked discussion.{% endif %} +{% ifversion discussions-closable %} +{% note %} + +**Note:** You can also close a discussion. For more information, see "[Closing a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#closing-a-discussion)." + +{% endnote %} +{% endif %} + {% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} 1. In the list of discussions, click the discussion you want to lock. diff --git a/data/features/discussions-closable.yml b/data/features/discussions-closable.yml new file mode 100644 index 0000000000..ba5aacc0f1 --- /dev/null +++ b/data/features/discussions-closable.yml @@ -0,0 +1,6 @@ +# Issues 9692 +# Docs for closing discussions +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.9' diff --git a/data/reusables/discussions/closing-discussions.md b/data/reusables/discussions/closing-discussions.md new file mode 100644 index 0000000000..2360bc57f4 --- /dev/null +++ b/data/reusables/discussions/closing-discussions.md @@ -0,0 +1 @@ +You can close a discussion when the discussion has been resolved, is no longer relevant, or is a duplicate. \ No newline at end of file