Skip to content

[General] Update issue tracker's duplicate resolution message#46743

Open
daverayment wants to merge 2 commits intomicrosoft:mainfrom
daverayment:patch-6
Open

[General] Update issue tracker's duplicate resolution message#46743
daverayment wants to merge 2 commits intomicrosoft:mainfrom
daverayment:patch-6

Conversation

@daverayment
Copy link
Copy Markdown
Collaborator

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 #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.

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

  • Closes: #xxx
  • Communication: I've discussed this with core contributors already. If the work hasn't been agreed, this work might be rejected
  • Tests: Added/updated and all pass
  • Localization: All end-user-facing strings can be localized
  • Dev docs: Added/updated
  • New binaries: Added on the required places
  • Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Original text:

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!

Updated:

We've identified this issue as a duplicate of an existing one and are closing this thread so discussion stays in one place.

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

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 daverayment requested a review from a team as a code owner April 3, 2026 02:13
@daverayment daverayment added the Area-GitHub workflow Issues regarding the GitHub workflow and automation label Apr 3, 2026
@niels9001 niels9001 enabled auto-merge (squash) April 3, 2026 09:19
@niels9001
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@niels9001 niels9001 closed this Apr 5, 2026
auto-merge was automatically disabled April 5, 2026 05:53

Pull request was closed

@niels9001 niels9001 reopened this Apr 5, 2026
@niels9001 niels9001 enabled auto-merge (squash) April 5, 2026 05:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-GitHub workflow Issues regarding the GitHub workflow and automation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants