From 812aa3fb0e337a0f9a4c98e8fd62f5a25180da07 Mon Sep 17 00:00:00 2001 From: boulais01 <89533621+boulais01@users.noreply.github.com> Date: Tue, 19 Sep 2023 14:29:01 -0500 Subject: [PATCH] fix: Update pull_request_template.md for title --- pull_request_template.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/pull_request_template.md b/pull_request_template.md index 1042b748..19853ee7 100644 --- a/pull_request_template.md +++ b/pull_request_template.md @@ -1,17 +1,19 @@ When creating a pull request to add a new feature or alter an existing one, there are some important elements to include to help our team review and process it more efficiently. -1. List the names of those who contributed to the project. +1. Make sure the title is descriptive of what the PR includes. Don't mention issue names/numbers; save that for the description. -2. Link the issue the pull request is meant to fix/resolve. +2. List the names of those who contributed to the project. -3. Describe the contents and goal of the pull request. +3. Link the issue the pull request is meant to fix/resolve. -4. Will coverge be maintained/increased? +4. Describe the contents and goal of the pull request. -5. What operating systems has this been tested on? How were these tests conducted? +5. Will coverge be maintained/increased? -6. Include a code block and/or screenshots displaying the functionality of your feature, if applicable/possible. +6. What operating systems has this been tested on? How were these tests conducted? + +7. Include a code block and/or screenshots displaying the functionality of your feature, if applicable/possible. Mark as a draft until it is ready to begin the reviewing process, then tag our [Lead Software Architect, Lauren Nevill](https://github.com/laurennevill), our [Principal Software Engineer, Bergas Batara](https://github.com/bergasanargya), and our [Founding Engineer, Gregory Kapfhammer](https://github.com/gkapfham)