These changes introduce new files for a pull request and issue templates in the .github directory.
Why this PR?
This is very important in a collaborative environment to have such templates thus having a common and consistent way of reporting issues and suggesting new features as well as documentation. It also helps a developer to fill up all the necessary information on their pull request without having to think of it themselves.
Which issue does it resolve?
Resolves #18
Dev Notes:
It's highly recommended not to skip any point listed in these templates. Doing so is considered as giving inaccurate information.
It's highly advised to set the necessary parameters on the right section of your PR when opening any pull requests. This includes:
Assigning reviewers
Converting the PR to draft when still in progress
Assigning the PR to yourself if you're the author
Setting as many labels as possible to communicate about your changes
Choosing the projects board your changes belong to as well as status and finally,
🚀 Pull Request
Changes Made:
These changes introduce new files for a pull request and issue templates in the
.githubdirectory.Why this PR?
This is very important in a collaborative environment to have such templates thus having a common and consistent way of reporting issues and suggesting new features as well as documentation. It also helps a developer to fill up all the necessary information on their pull request without having to think of it themselves.
Which issue does it resolve?
Resolves #18
Dev Notes:
It's highly advised to set the necessary parameters on the right section of your PR when opening any pull requests. This includes:
projectsboard your changes belong to as well asstatusand finally,Design Notes:
None for now.
Checklist: