punkfairie/odin-css-exercises
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update PULL_REQUEST_TEMPLATE.md

Browse source
This commit is contained in:
Eric Olkowski 2022-01-23 01:13:08 -05:00 committed by GitHub
parent f50e1e6216
commit 7f0943d463
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
.github/PULL_REQUEST_TEMPLATE.md vendored
View file

@ -1,17 +1,15 @@
<!-- <!--
Thank you for taking the time to contribute to The Odin Project. In order to get PRs closed in a reasonable amount of time, we request that you include a baseline of information about the changes you are proposing. Please complete each applicable checkbox and answer the following triage questions: Thank you for taking the time to contribute to The Odin Project. In order to get pull requests (PR) closed in a reasonable amount of time, you must include a baseline of information about the changes you are proposing. Please complete each applicable checkbox and answer the following triage questions:
--> -->
- [ ] You have read our [CSS Exercises Contributing Guide](https://github.com/TheOdinProject/css-exercises/blob/main/CONTRIBUTING.md). - [ ] You have thoroughly read our [CSS Exercises Contributing Guide](https://github.com/TheOdinProject/css-exercises/blob/main/CONTRIBUTING.md).
- [ ] The title states the exercise being changed and what the change is using the `exercise: summary of changes` scheme. For example: "01-flex-layout: updated solution CSS" or "grid exercises: fixed naming scheme". - [ ] The title of this PR is in `file/exercise/folder: brief description of changes` format, e.g. `01 flex center: add hint for XYZ`
- [ ] If the PR is related to an open issue, link the issue to your pull request. See [Using keywords in issues and pull requests](https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests) for more info. - [ ] If the PR is related to an open issue, link the issue to the PR by replacing `XXXXX` in Step 2 below with the issue number, e.g. `#2013`.
- [ ] If changes are requested, please make the changes in a timely manner. After you submit the changes, request another review from the maintainer (top right). - [ ] If changes are requested, please make the changes in a timely manner. After you submit the changes, request another review from the maintainer (top of the right sidebar).
**1. Description of the Changes**
<!-- A clear and concise description of your changes. Also include why you are proposing these changes, such as if it is related to an open issue or another reason. -->
#### 1. Describe the changes made and include why they are necessary or important: **2. Related Issue**
...your text here
#### 2. Related Issue
Closes #XXXXX Closes #XXXXX