95e6f3d3ab
* add 3.1 to deprecated versions * rewrite img src to use azure blob storage in archive script Co-authored-by: rachmari <rachmari@users.noreply.github.com> * remove static files for ghes 3.1 * remove liquid conditionals and content for ghes 3.1 * remove outdated hardware reqs reusable * Fix liquid conditional uncaught by script * Close liquid conditionals missed by script * Apply @mattpollard's suggestions Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> Co-authored-by: rachmari <rachmari@users.noreply.github.com> Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
24 lines
1.4 KiB
Markdown
24 lines
1.4 KiB
Markdown
### Resolving conversations
|
|
|
|
You can resolve a conversation in a pull request if you opened the pull request or if you have write access to the repository where the pull request was opened.
|
|
|
|
To indicate that a conversation on the **Files changed** tab is complete, click **Resolve conversation**.
|
|
|
|
|
|
|
|
The entire conversation will be collapsed and marked as resolved, making it easier to find conversations that still need to be addressed.
|
|
|
|
|
|
|
|
If the suggestion in a comment is out of your pull request's scope, you can open a new issue that tracks the feedback and links back to the original comment. For more information, see "[Opening an issue from a comment](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)."
|
|
|
|
{% ifversion fpt or ghes or ghae-issue-4382 or ghec %}
|
|
#### Discovering and navigating conversations
|
|
|
|
You can discover and navigate to all the conversations in your pull request using the **Conversations** menu that's shown at the top of the **Files Changed** tab.
|
|
|
|
From this view, you can see which conversations are unresolved, resolved, and outdated. This makes it easy to discover and resolve conversations.
|
|
|
|
|
|
{% endif %}
|