Frecuentemente publicamos actualizaciones de nuestra documentación. Es posible que la traducción de esta página esté en curso. Para conocer la información más actual, visita la documentación en inglés. Si existe un problema con las traducciones en esta página, por favor infórmanos.

Moderating discussions

You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, and converting issues to discussions. and editing or deleting comments, discussions, and categories that don't align with your community's code of conduct to discussions.

People with triage access to a repository can moderate discussions in the repository.

En este artículo

Note: GitHub Discussions is currently in beta and subject to change.

About moderating discussions

Discussions are an open forum for conversation among maintainers and the community for a project on GitHub. If you have triage permissions for a repository, you can help moderate a project's discussions by marking comments as answers, locking discussions that are not longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development.

Marking a comment as an answer

You can mark a comment in the discussion as an answer to the discussion if a discussion is within a category that accepts answers. For more information, see "About discussions."

When you mark a question as an answer, GitHub will highlight the comment and replies to the comment to help visitors quickly find the answer.

Comment marked as answer to a discussion

You can't mark a threaded comment in response to a comment as the answer to a discussion. You also can't mark a minimized comment as the answer to a discussion.

  1. En GitHub, visita la página principal del repositorio.
  2. Under your repository name, click Discussions. "Discussions" tab for a repository
  3. In the list of discussions, click the unanswered discussion you want to mark as answered. Unanswered discussion
  4. In the discussion, find the comment you want to mark as the answer.
  5. In the upper-right corner of the comment, click . "Mark as answer" circular check icon for marking comment as answer in a discussion
  6. Optionally, to unmark a comment as the answer, click .

Locking discussions

It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or GitHub's 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 will still be able to comment on the discussion.

  1. En GitHub, visita la página principal del repositorio.
  2. Under your repository name, click Discussions. "Discussions" tab for a repository
  3. In the list of discussions, click the discussion you want to lock. Lock discussion
  4. In the right margin of a discussion, click Lock conversation.
  5. Read the information about locking conversations and click Lock conversation on this discussion.
  6. When you're ready to unlock the conversation, click Unlock conversation, then click Unlock conversation on this discussion.

Converting an issue to a discussion

When you convert an issue to a discussion, the discussion is automatically created using the content from the issue. People with write access to a repository can bulk convert issues based on labels. For more information, see "Managing discussions in your repository."

  1. En GitHub, visita la página principal del repositorio.
  2. Debajo del nombre de tu repositorio, da clic en Informe de problemas. Pestaña de informe de problemas
  3. In the list of issues, click the issue you'd like to convert.
  4. In the right margin of an issue, click Convert to discussion.
  5. Select the Choose a category drop-down menu, and click a category for your discussion.
  6. Click I understand, convert this issue to a discussion.

Did this doc help you? Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

O, learn how to contribute.