docs: update pull requests docs to include a how to ask section

[sfavello]

PR Checklist

• Addresses an existing open issue: fixes Docs: Mention how to ask for help with PRs #6584
• That issue was marked as accepting prs
• Steps in Contributing were taken

Overview

Added a how to ask section in pull request docs. I wasn't sure what the title section should be. I might be overthinking it, but labeling it ask "How to ask for help" felt too specific. People might not be just asking for help but wanting to ask questions (to gain insight, clarification, etc). Again I might be overthinking it. 😅

[typescript-eslint]

Thanks for the PR, @sfavello!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!

---

🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint.

[netlify]

✅ Deploy Preview for typescript-eslint ready!

Name	Link
🔨 Latest commit	3befe6e
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/6431e3ce3141440008c97d95
😎 Deploy Preview	https://deploy-preview-6872--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 3befe6e. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 25 targets

• Node 18 - nx test utils
• Node 18 - nx test visitor-keys
• Node 18 - nx run-many --target=build --parallel --exclude website
• Node 18 - nx test type-utils
• nx run-many --target=typecheck --parallel
• Node 18 - nx test eslint-plugin-tslint
• Node 14 - nx test typescript-estree --coverage=false
• Node 14 - nx run-many --target=build --parallel --exclude website
• Node 14 - nx test eslint-plugin-tslint --coverage=false
• Node 14 - nx test ast-spec --coverage=false
• nx run-many --target=build --parallel --exclude website
• Node 18 - nx test typescript-estree
• Node 14 - nx test utils --coverage=false
• Node 18 - nx test eslint-plugin
• Node 14 - nx test eslint-plugin --coverage=false
• Node 18 - nx test eslint-plugin-internal
• Node 14 - nx test scope-manager --coverage=false
• Node 14 - nx test eslint-plugin-internal --coverage=false
• nx run-many --target=lint --parallel
• Node 18 - nx test ast-spec
• Node 14 - nx test visitor-keys --coverage=false
• Node 18 - nx test scope-manager
• Node 18 - nx test parser
• Node 14 - nx test type-utils --coverage=false
• Node 14 - nx test parser --coverage=false

---

Sent with 💌 from NxCloud.

[JoshuaKGoldberg]

LGTM in general! A couple of suggestions for touching up the wording, would love your thoughts.

[JoshuaKGoldberg]

Btw @sfavello we normally put the PR description in the body text after Overview, where it's commented <!-- Description of what is changed and how the code change does that. -->. I went ahead and edited this PR. Very small thing 😄

[JoshuaKGoldberg]

(lil grammar nit since the heading is updated)

Suggested change

	If you need help and/or have a question, posting a comment in the PR is a great way to do so.
	If you need help and/or have a question, posting a comment in the PR is a great way to ask.

[JoshuaKGoldberg]

🔥 great! Thanks for iterating on this @sfavello!