add issue and pull request templates (#819)

* feat(all) - Add issue and pull ruequest templates

* Update PULL_REQUEST_TEMPLATE.md

* Create COMMIT_GUIDELINES.md

* Update PULL_REQUEST_TEMPLATE.md

* Update PULL_REQUEST_TEMPLATE.md

* Update COMMIT_GUIDELINES.md
This commit is contained in:
Sara Vieira 2017-10-30 17:12:00 +00:00 committed by GitHub
parent 5ebce8fdea
commit f7eb8a276c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 71 additions and 0 deletions

25
.github/COMMIT_GUIDELINES.md vendored Normal file
View File

@ -0,0 +1,25 @@
# Commit Guidelines
```
<type><(scope)?>: <msg>
```
Where type is one of:
```
build
chore
ci
docs
feat
fix
perf
refactor
revert
style
test
```
And where scope is one of ui-toolkit, my-joy-beta, cloudapi-gql, boilerplate, and create-instance.
*The recommended method to commit should be by running npm run commit.*

24
.github/ISSUE_TEMPLATE.md vendored Normal file
View File

@ -0,0 +1,24 @@
* **I'm submitting a ... **
- [ ] bug report
- [ ] feature request
- [ ] design request
* **What is the current behavior?**
* **If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem**
* **What is the expected behavior?**
* **What is the motivation / use case for changing the behavior?**
* **If the current behavior is a bug, please provide your browser**
* **Other information**

22
.github/PULL_REQUEST_TEMPLATE.md vendored Normal file
View File

@ -0,0 +1,22 @@
* **Please check if the PR fulfills these requirements**
- [ ] The commit message follows our [guidelines](https://github.com/yldio/joyent-portal/blob/issue-template/.github/COMMIT_GUIDELINES.md)
- [ ] Tests for the changes have been added (for bug fixes / features)
* **What kind of change does this PR introduce?** (Bug fix, feature, docs update, ...)
* **Does this PR close an issue?** (If not please create one)
* **What is the new behavior (if this is a feature change)?**
* **Does this PR introduce a breaking change?** (What changes might users need to make in their application due to this PR?)
* **Other information**: