* updated dead link and added an example gif replaced CONTRIBUTING.md#create-a-pull-request with the current one. * Update PULL_REQUEST_TEMPLATE.md resolved the change previously made * Update .github/PULL_REQUEST_TEMPLATE.md Co-authored-by: Julianna Tetreault <32834804+juliannatetreault@users.noreply.github.com> Co-authored-by: Julianna Tetreault <32834804+juliannatetreault@users.noreply.github.com>
3.9 KiB
3.9 KiB
What type of PR is this? (check all applicable)
- Refactor
- Feature
- Bug Fix
- Optimization
- Documentation Update
Description
Related Tickets & Documents
- Related Issue #
- Closes #
QA Instructions, Screenshots, Recordings
Please replace this line with instructions on how to test your changes, a note on the devices and browsers this has been tested on, as well as any relevant images for UI changes.
UI accessibility concerns?
If your PR includes UI changes, please replace this line with details on how accessibility is impacted and tested. For more info, check out the Forem Accessibility Docs.
Added/updated tests?
- Yes
- No, and this is why: please replace this line with details on why tests have not been included
- I need help with writing tests
[Forem core team only] How will this change be communicated?
Will this PR introduce a change that impacts Forem members or creators, the development process, or any of our internal teams? If so, please note how you will share this change with the people who need to know about it.
- I've updated the Developer Docs or Storybook (for Crayons components)
- This PR changes the Forem platform and our documentation needs to be updated. I have filled out the Changes Requested issue template so Community Success can help update the Admin Docs appropriately.
- I've updated the README or added inline documentation
- I've added an entry to
CHANGELOG.md - I will share this change in a Changelog or in a forem.dev post
- I will share this change internally with the appropriate teams
- I'm not sure how best to communicate this change and need help
- This change does not need to be communicated, and this is why not: please replace this line with details on why this change doesn't need to be shared