-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
af93b1d
commit e365593
Showing
1 changed file
with
54 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,54 @@ | ||
| <!-- | ||
| For Work In Progress Pull Requests, please use the Draft PR feature, | ||
| see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details. | ||
| For a timely review/response, please avoid force-pushing additional | ||
| commits if your PR already received reviews or comments. | ||
| Before submitting a Pull Request, please ensure you've done the following: | ||
| - 📖 Read the Forem Contributing Guide: https://developers.forem.com/contributing-guide/forem#create-a-pull-request | ||
| - 📖 Read the Forem Code of Conduct: https://github.com/forem/forem/blob/main/CODE_OF_CONDUCT.md | ||
| - 👷♀️ Create small PRs. In most cases this will be possible. | ||
| - ✅ Provide tests for your changes. | ||
| - 📝 Use descriptive commit messages. | ||
| - 📗 Update any related documentation and include any relevant screenshots. | ||
| NOTE: Pull Requests from forked repositories will need to be reviewed by | ||
| a Forem Team member before any CI builds will run. Once your PR is approved | ||
| with a `/ci` reply to the PR, it will be allowed to run subsequent builds without | ||
| manual approval. | ||
| --> | ||
|
|
||
| ## What type of PR is this? (check all applicable) | ||
|
|
||
| - [ ] Refactor | ||
| - [ ] Feature | ||
| - [ ] Bug Fix | ||
| - [ ] Optimization | ||
| - [ ] Documentation Update | ||
|
|
||
| ## Description | ||
|
|
||
| ## Related Tickets & Documents | ||
|
|
||
| <!-- | ||
| For pull requests that relate or close an issue, please include them | ||
| below. We like to follow [Github's guidance on linking issues to pull requests](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue). | ||
| For example having the text: "closes #1234" would connect the current pull | ||
| request to issue 1234. And when we merge the pull request, Github will | ||
| automatically close the issue. | ||
| --> | ||
|
|
||
| - Related Issue # | ||
| - Closes # | ||
|
|
||
| ## 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 | ||
|
|
||
| ## [optional] Are there any post deployment tasks we need to perform? | ||
|
|