프로젝트 구조 세팅 #1
Description
💡 Feature proposal : Submit-up Design System Setup
Use-cases
- Issue & PR Template 생성
- Bug Template 생성
Example
Attempted solutions
-
.github 파일에 넣을 예정입니다.
-
Issue Tempalate
- Feature.md
---
name: Feature Proposal
about: Tell us how Copybara Action can serve you better
labels: enhancement
---
<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the existing
issues and verify the issue you're about to submit isn't a duplicate.
--->
## :bulb: Feature proposal
### Use-cases
<!---
In order to properly evaluate a feature request, it is necessary to understand the
use-cases for it. Please describe below the _end goal_ you are trying to achieve
that has led you to request this feature. Please keep this section focused on the
problem and not on the suggested solution. We'll get to that in a moment, below!
--->
### Example
<!--- Please provide an example for how this feature would be used --->
### Attempted solutions
<!---
If you've already tried to solve the problem with existing features and found a limitation
that prevented you from succeeding, please describe it below in as much detail as possible.
--->
### Proposal
<!---
If you have an idea for a way to address the problem, please describe it below.
If you're not sure of some details, don't worry! When we evaluate the feature request we may
suggest modifications as necessary to work within the design constraints of the project.
--->
<!-- project-feature -->
### References
<!--
Are there any other GitHub issues, whether open or closed, that are related to the problem
you've described above or to the suggested solution? If so, please create a list below that
mentions each of them. For example:
- #123
- #456
--->
- Bug.md
---
name: Bug Report
about: Report an issue you found with Copybara Action
labels: bug
---
<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the existing
issues and verify the issue you're about to submit isn't a duplicate.
--->
## :beetle: Bug report
### Summary
<!--- Summarize the bug encountered concisely --->
### Expected behavior
<!--- What SHOULD HAVE happened --->
### Actual behavior
<!--- What happened. You can include screenshots or video recordings --->
### Steps to reproduce the problem
<!---
Please include as much details as possible so we can reproduce the
bug and fix it quickly - This is very important
--->
<!-- project-bug -->
### Environment
<!---
Please include any relevant details about the version of Copybara Action you
are using, your operating system, browser, etc.
--->
- Version:
### Possible fix
<!---
If you can think of any possible solution to fix the bug.
If you can be technical about the possible resolution, please do so
--->
- PR Template
# Pull request
<!---
IMPORTANT: Please do not create a Pull Request without first creating an issue and
reading our contributing guidelines (docs/CONTRIBUTING.md)
You can skip this if you're fixing a typo.
--->
## Related issue
<!---
Copybara Action only accepts pull requests related to open issues
If suggesting a new feature or change, please discuss it in an issue first
If fixing a bug, there should be an issue describing it with steps to reproduce
Please link to the issue here
-->
## Motivation and context
<!---
Explain the context and why you're making that change. What is the
problem you're trying to solve? In some cases there is not a problem
and this can be thought of being the motivation for your change.
--->
## Solution
<!---
Describe the modifications you've done.
What will change as a result of your pull request?
--->
## 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.
If this change has an impact on UX, include screenshots or a video.
--->
<!-- project-pull-request -->
## 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.
- [ ] I have read the **docs/CONTRIBUTING.md** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.Proposal
x