This PR brings in a new folder, ".github" which is described here
Basically 3 things are done here:
Move Contributing.md to the .github folder.
Create an issue template
Create a Pull-request template (Which this PR is following)
Related Issue(s)
Closes #166
Motivation and Context
As the project grows, communication across contributors is vital to its success. Hopefully, with a little conformity, we can make it a little easier on everybody.
How Has This Been Tested?
Only time will tell on this.
AKA, testing this will be done by essentially usability testing. <- WE are the users.
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[X] Chore (documentation, refactoring, basically not a feature or a bug fix)
Checklist:
[ ] My code follows the code style of this project.
[X] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
Of course, as always, this is merely MY opinion on how this should look. With this PR, I know ask YOU what you think. Any suggestions?
Description
This PR brings in a new folder, ".github" which is described here Basically 3 things are done here:
Related Issue(s)
Closes #166
Motivation and Context
As the project grows, communication across contributors is vital to its success. Hopefully, with a little conformity, we can make it a little easier on everybody.
How Has This Been Tested?
Only time will tell on this. AKA, testing this will be done by essentially usability testing. <- WE are the users.
Types of changes
Checklist:
Of course, as always, this is merely MY opinion on how this should look. With this PR, I know ask YOU what you think. Any suggestions?