Pr template

[kamilahjae]

Purpose

To add a template to each PR to reduce the need of copy/pasting the summary text

What the code is doing

Each time a PR is created a code author will see:

• A link to the PR etiquette doc
  *Pre-populated PR headers with explanation text inspired by the screenshot found in the PR Etiquette cheat sheet
  *Adds a testing section. I think adding this section is helpful because it shows how we are maintaining our code and also shows reviewers how they can replicate testing if they desire.

Testing

This has been added to the CENACS repo as well.

Where to look

This file will live at the root directory of this repo.

Usage Example/Visuals

N/A

Time estimate
~5min or less. Feedback is welcome! Specifically on whether or not this is useful. Also, I'm not committed to any of the example text. I'm open to changing any of the text and adding/removing info.

[kasparm]

Thank you for helping out and creating this template for PostREISE. This will make the teams live easier.
I have two small things.
First, please follow the commit message standards we are using. See https://github.com/Breakthrough-Energy/REISE/wiki/Software-Development-Guidelines#semantic-commit-messages
Second, please hide the pull_request_template in the .github/ folder. You will have to create that folder.

[kamilahjae]

@kasparm should the develop or master branch be rebased into this one? I rebased develop into this feature branch, but realized this PR is to merge into master. I think this could pose problems, no?

[rouille]

@kasparm should the develop or master branch be rebased into this one? I rebased develop into this feature branch, but realized this PR is to merge into master. I think this could pose problems, no?

Your branch should be merged into develop. We don't use master.

[kasparm]

Looks good, thank you. Make sure to rebase before merging.