[General] Update issue tracker's duplicate resolution message#46743
Closed
daverayment wants to merge 2 commits into
Closed
[General] Update issue tracker's duplicate resolution message#46743daverayment wants to merge 2 commits into
daverayment wants to merge 2 commits into
Conversation
Update dupe message to include reference to the comment above, as it can be confusing to newcomers to not have it pointed out. Slightly tightened up wording.
daverayment
added
the
Area-GitHub workflow
niels9001
approved these changes
Apr 3, 2026
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the GitHub issue management policy’s duplicate-resolution reply to make the original tracking issue easier for newcomers to find.
Changes:
- Rewords the duplicate closure message for clarity.
- Adds guidance to look at the prior duplicate command/comment for the original tracking issue link.
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
niels9001
approved these changes
May 18, 2026
Collaborator
|
Seems like the CI is not allowing us to merge this PR. Trying it again in #47981 |
auto-merge was automatically disabled
May 19, 2026 08:41
Pull request was closed
yeelam-gordon
pushed a commit
that referenced
this pull request
May 26, 2026
Reopens the change from #46743 (which appears to be broken) on a fresh branch. Original author: @daverayment ## Summary GitHub newcomers can be confused by the current duplicate resolution message, as it doesn't clearly point to the original referenced issue - see #46347 (comment). They may not realise that the #12345 in the duplicate comment is the relevant link. This small wording update to the duplicate resolution message tightens up wording slightly and includes reference to the prior `/dup #nnn` comment so newcomers don't miss it. ### Before > Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! ### After > We've identified this issue as a duplicate of an existing one and are closing this thread so discussion stays in one place.<br/><br/>Please see the comment above for the link to the original tracking issue, and feel free to subscribe there for updates. ## Validation Steps Performed N/A - bot reply text change only. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GitHub newcomers can be confused by the current duplicate resolution message, as it doesn't include a reference to the original issue - see #46347 (comment). They may not realise that the
#12345in the duplicate comment is the relevant link.This small wording update to the duplicate resolution message tightens up wording slightly and includes reference to the prior
/dup #nnncomment so newcomers don't miss it.Note: I'm assuming we cannot reference the issue number itself. I can't access the GitHub bot's documentation pages to check.
Summary of the Pull Request
PR Checklist
Detailed Description of the Pull Request / Additional comments
Original text:
Updated:
Validation Steps Performed
N/A