You can follow the instructions here for issues and pull requests. However, these instructions use the GitHub interface. If you are new to git, the recommendation is to go through the normal process of creating a branch locally, adding the files in markdown in a folder called .github, and opening a new pull request for the team to review (for practice's sake :)).
Details
We want all issues and pull request templates to allow for succinct but detailed enough communication, that anyone can pick up a ticket and it make sense without having to speak to a human. Obviously, interaction with the team is highly recommended but issues should be reasonably self-explanatory.
Look at some of our closed issues / PRs to figure out what's worked best in terms of headings /content to display in the template.
What
We want to create GitHub issue and pull request templates to keep our team comms consistent and save time.
How
You can follow the instructions here for issues and pull requests. However, these instructions use the GitHub interface. If you are new to git, the recommendation is to go through the normal process of creating a branch locally, adding the files in markdown in a folder called .github, and opening a new pull request for the team to review (for practice's sake :)).
Details