fix: missing paren in link in "Resolving a merge conflict on GitHub"#12009
fix: missing paren in link in "Resolving a merge conflict on GitHub"#12009ramyaparimi merged 2 commits intogithub:mainfrom
Conversation
|
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
Automatically generated comment ℹ️This comment is automatically generated and will be overwritten every time changes are committed to this branch. The table contains an overview of files in the Content directory changesYou may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
|
|
@ramyaparimi, if this was for the missing PR description (and issue), that's my bad—it seems making a PR through GitHub.dev totally bypasses any option to fill out the description. See also the now-linked issue. Note that I cannot self-review or check the generated content as the staged version is no longer live. |
|
@perryprog Thanks so much for clarifying ✨ Description and linking issue helps a lot during triaging 💖 |
|
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
Why:
Closes #12019
What's being changed:
I've added the missing paren to the markdown's link.
Check off the following:
Writer impact (This section is for GitHub staff members only):