The Markdown formatting is not ignored in the issue title using the escape character. Example: \test\.

[5AbhishekSaxena]

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?

File: https://github.com/github/docs/blob/main/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md#ignoring-markdown-formatting

Page: https://github.com/github/docs/blob/main/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md#ignoring-markdown-formatting

The above-mentioned section talks about how one can tell Github to ignore the Markdown by using \ but using this character. This works everywhere but not in the title of the issue and I am assuming in the title of the PRs.

An example of the issue is in the title of this issue itself.

What changes are you suggesting?

The Github should acknowledge the escape character (\) as it does at the other places and allow the users to ignore the Markdown formatting in the title of the issues.

Additional information

No response

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

[steveward]

Thanks for the issue @5AbhishekSaxena, I'll get this triaged for 👀

[5AbhishekSaxena]

No problem @steveward, happy to contribute 😁.

[skedwards88]

Thanks for opening this issue! You or anyone else is welcome to note this exception in the docs.

[5AbhishekSaxena]

I was thinking instead of adding this exception in the docs, the issue should be fixed in the code itself where the backticks are processed which formats the title of the issue/pull but acknowledge the escaping character, and skip the formatting.

[cmwilson21]

@5AbhishekSaxena - Here in this repo, we work on the documentation site and articles. For now, the best fix is to update the docs to the behavior.

The best place to leave feedback for the change in behavior you are suggesting would likely be with the Issues team here.

[5AbhishekSaxena]

I have raised a PR which adds a note informing the user about the issue. I have also started a discussion on the community page which can be found here: https://github.com/orgs/community/discussions/54689.