소스 검색

feat: Add PR and issue templates.

pull/376/head
Robson Cruz 4 년 전
부모
커밋
13eaacc87f
4개의 변경된 파일75개의 추가작업 그리고 0개의 파일을 삭제
  1. +33
    -0
      .github/ISSUE_TEMPLATE/bug_report.md
  2. +1
    -0
      .github/ISSUE_TEMPLATE/config.yml
  3. +13
    -0
      .github/ISSUE_TEMPLATE/feature_request.md
  4. +28
    -0
      .github/pull_request_template.md

+ 33
- 0
.github/ISSUE_TEMPLATE/bug_report.md 파일 보기

@@ -0,0 +1,33 @@
<!--- Provide a general summary of the issue in the Title above -->

## Description
<!--- Provide a more detailed introduction to the issue itself, and why you consider it to be a bug -->

## Expected Behavior
<!--- Tell us what should happen -->

## Actual Behavior
<!--- Tell us what happens instead -->

## Possible Fix
<!--- Not obligatory, but suggest a fix or reason for the bug -->

## Steps to Reproduce
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
<!--- reproduce this bug. Include code to reproduce, if relevant -->
1.
2.
3.
4.

## Context
<!--- How has this bug affected you? What were you trying to accomplish? -->

## Screenshot
<!--- If applicable -->


## Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->
* Version used:
* Operating System and version:

+ 1
- 0
.github/ISSUE_TEMPLATE/config.yml 파일 보기

@@ -0,0 +1 @@
blank_issues_enabled: false

+ 13
- 0
.github/ISSUE_TEMPLATE/feature_request.md 파일 보기

@@ -0,0 +1,13 @@
<!--- Provide a general summary of the issue in the Title above -->

## Detailed Description
<!--- Provide a detailed description of the change or addition you are proposing -->

## Context
<!--- Why is this change important to you? How would you use it? -->
<!--- How can it benefit other users? -->

## Possible Implementation
<!--- Not obligatory, but suggest an idea for implementing addition or change -->



+ 28
- 0
.github/pull_request_template.md 파일 보기

@@ -0,0 +1,28 @@
<!--- Provide a general summary of your changes in the Title above -->

## Description
<!--- Describe your changes in detail -->

## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->
<!--- If it fixes an open issue, please link to the issue here. -->

## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->

## Screenshots (if appropriate):

## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] 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)

## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.

불러오는 중...
취소
저장