Question

A repository maintainer notices that one open issue has grown into a lengthy back-and-forth where community members are debating the general direction of a feature, rather than reporting a specific, actionable bug. The maintainer wants to keep the actionable tracking work separate from the broader community conversation. Which action best fits GitHub's intended collaboration model?

Accepted Answer

Convert the issue into a discussion so the open-ended conversation lives in Discussions, while keeping issues focused on trackable work

Answer

Lock the issue immediately so no further comments can be added by anyone

Answer

Create a Gist containing the conversation and share the link with the participants

Answer

Add the debate to the repository Wiki so it is preserved as project documentation