-
Notifications
You must be signed in to change notification settings - Fork 61.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mention that pull requests cannot use issue forms #8702
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. |
@Calinou Thanks so much for opening a PR! I'll get this triaged for review ⚡ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👋🏼 @Calinou, thanks for creating this PR! I think this information can definitely help people who might try to use issue forms with pull requests. I've made just a few minor changes to align the content with our style guide. I'm going to update the branch and will get this merged as soon as all the checks are passing.
Thanks for contributing to the GitHub docs! ⚡
...ities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
Outdated
Show resolved
Hide resolved
- OS: | ||
- Node: | ||
- npm: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch on the spacing here 😁
…-and-pull-requests/syntax-for-issue-forms.md
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 #8701
What's being changed:
Add a mention that pull requests cannot use issue forms, but only traditional pull request templates. (Correct me if I'm wrong 🙂)
Check off the following:
Writer impact (This section is for GitHub staff members only):