doc/user/discussions/_index.md
{{< details >}}
{{< /details >}}
{{< history >}}
wiki_comments. Disabled by default.wiki_comments removed.{{< /history >}}
GitLab encourages communication through comments, threads, and suggesting changes for code. Comments support Markdown and quick actions.
Two types of comments are available:
You can suggest code changes in your commit diff comment, which the user can accept through the user interface.
You can create comments in places like:
Each object can have as many as 5,000 comments.
You can mention a user or a group (including subgroups) in your GitLab
instance with @username or @groupname. GitLab notifies all mentioned users with to-do items and emails.
Users can change this setting for themselves in the notification settings.
You can quickly see which comments involve you, because GitLab highlights mentions for yourself (the current, authenticated user) in a different color.
When you mention someone, in a work item or merge request, they become a participant.
{{< history >}}
disable_all_mention introduced in GitLab 16.1. Disabled by default. Enabled on GitLab.com.{{< /history >}}
[!flag] The availability of this feature is controlled by a feature flag. For more information, see the history.
Avoid mentioning @all in comments and descriptions. @all mentions more than
just the participants of the project, issue, or merge request, but all members
of that project's parent group. All these users receive an email notification
and a to-do item, and might interpret it as spam.
When you enable this feature flag, typing @all in comments and descriptions
results in plain text instead of mentioning all users.
When you disable this feature, existing @all mentions in the Markdown texts are unchanged,
and remain as links. Only future @all mentions appear as plain text.
You can disable notifications and mentions in group settings.
When you mention a group in a comment, every member of the group gets a to-do item added to their to-do list.
@ followed by the user, group, or subgroup namespace.
For example, @alex, @alex-team, or @alex-team/marketing.GitLab creates a to-do item for all the group and subgroup members.
For more information, see mention subgroups.
When you add comments to a merge request diff, these comments persist, even when you:
To add a commit diff comment:
The comment displays on the merge request's Overview tab.
The comment is not displayed on your project's Code > Commits page.
[!note] When your comment contains a reference to a commit included in the merge request, it's converted to a link in the context of the merge request. For example,
28719b171a056960dfdc0012b625d0b47b123196becomes28719b17that links tohttps://gitlab.example.com/example-group/example-project/-/merge_requests/12345/diffs?commit_id=28719b171a056960dfdc0012b625d0b47b123196.
If you have "reply by email" configured, you can reply to comments by sending an email.
You can use Markdown and quick actions in your email replies.
Email replies that create standard or threaded comments are subject to a two year retention policy.
You can edit your own comment at any time. Anyone with the Maintainer or Owner role can also edit a comment made by someone else.
To edit a comment:
{{< history >}}
email_on_added_mentions. Disabled by default.email_on_added_mentions removed.{{< /history >}}
By default, when you mention a user, GitLab creates a to-do item for them, and sends them a notification email.
If you edit an existing comment to add a user mention that wasn't there before, GitLab:
You can prevent public comments in an issue or merge request. When you do, only project members can add and edit comments.
Prerequisites:
To lock an issue or merge request:
GitLab adds a system note to the page details.
You must unlock all locked discussions in closed issues or merge requests before you can reopen the issue or merge request.
Only users with permission to access a confidential item receive notifications for comments on the item. If the item was not previously confidential, users without access may appear as participants. These users do not receive notifications while the item is confidential.
Who can be notified:
{{< history >}}
{{< /history >}}
Use internal notes to protect information added to a public issue, epic, wiki page, or merge request. Internal notes differ from public comments:
Prerequisites:
To add an internal note:
You can also mark an entire issue as confidential, or create confidential merge requests.
In discussions with many comments, filter the discussion to show only comments or history of changes (system notes). System notes include changes to the description, mentions in other GitLab objects, or changes to labels, assignees, and the milestone. GitLab saves your preference, and applies it to every issue, merge request, or epic you view.
Reverse the default order and interact with the activity feed sorted by most recent items at the top. GitLab saves your preference in local storage and applies it to every issue, merge request, or epic you view. Issues and epics share the same sorting preference, while merge requests maintain their own separate preference.
To change the activity sort order:
{{< details >}}
{{< /details >}}
You can see changes to the description listed in the history.
To compare the changes, select Compare with previous version.
You can assign an issue to a user who made a comment.
When you reply to a standard comment, you create a thread.
Prerequisites:
To create a thread by replying to a comment:
GitLab converts the top comment to a thread.
You can create a thread without replying to a standard comment.
Prerequisites:
To create a thread:
{{< history >}}
resolvable_issue_threads. Disabled by default.resolvable_issue_threads removed.{{< /history >}}
When a conversation is complete, you can resolve the thread. Resolved threads are collapsed, but users can still add comments.
Resolved threads can be reopened later by any user who has permission to resolve threads. To reopen a resolved thread, expand the thread and select Reopen thread.
Prerequisites:
To resolve a thread:
The same actions can be performed to reopen a thread.
Merge requests provide more flexible thread management options, such as:
{{< details >}}
{{< /details >}}
{{< collapsible title="Model information" >}}
{{< /collapsible >}}
{{< history >}}
summarize_notes_with_duo. Disabled by default.{{< /history >}}
Generate a summary of discussions on an issue.
<i class="fa-youtube-play" aria-hidden="true"></i> Watch an overview
<!-- Video published on 2024-03-28 -->Prerequisites:
To generate a summary of issue discussions:
The comments in the issue are summarized in as many as 10 list items. You can ask follow up questions based on the response.
Data usage: When you use this feature, the text of all comments on the issue are sent to the large language model.