Close as duplicate undocumented

[CommanderStorm]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

https://github.com/github/docs/blob/main/content/issues/tracking-your-work-with-issues/administering-issues/marking-issues-or-pull-requests-as-a-duplicate.md

(or in the github docs: https://docs.github.com/en/issues/tracking-your-work-with-issues/administering-issues/marking-issues-or-pull-requests-as-a-duplicate)

What part(s) of the article would you like to see updated?

A new button has spawned on the github close-issue page (BUT NOT PRs):

This button does the following (which is much better than before):

Here to the question:
How should this be documented? Current documentation assumes that both PRs and Issues behave the same on this feature.

=> given that you people have access to the "internal roadmap" or know if adding this to PRs is planned in the short term, I thought it better to create an issue rather than bother you with a soon-outdated version of a PR differentiating issue-duplicates from PR-duplicates

Additional information

The feature seems to be semi-randomly toggled on and off every few hours for the last week.

=> Ommitting this from the docs might be intentional on you peoples part

[welcome]

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[nguyenalex836]

@CommanderStorm Thank you for opening this issue! ✨

After some digging, it looks like the Close as duplicate option is actually behind a feature preview for the "New Issues Experience", which is why it hasn't been documented yet.

Once that option leaves feature preview and becomes available to all users, the documentation should be updated to reflect that new option 💛 Thank you for your diligence and ensuring this is on our radar! I'll go ahead and close this issue, but please let us know if you have any other comments.

[CommanderStorm]

Ah sorry about that.

It was not listed in the "New issus experience" blog post