Skip to content

Commit 69607cf

Browse files
authored
Merge pull request #95 add github templates
2 parents 62c28b2 + fd19d91 commit 69607cf

File tree

4 files changed

+114
-0
lines changed

4 files changed

+114
-0
lines changed
Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
---
2+
name: Bug Report
3+
about: Create a report to help YDB Python SDK to improve
4+
title: "bug: "
5+
labels: "bug"
6+
assignees: ""
7+
8+
---
9+
10+
# Bug Report
11+
12+
**YDB GO Python version:**
13+
14+
<!-- Please specify commit or tag version. -->
15+
16+
**Environment**
17+
18+
<!-- Please specify Operation System, Python version, CPU architecture -->
19+
20+
**Current behavior:**
21+
22+
<!-- Describe how the bug manifests. -->
23+
24+
**Expected behavior:**
25+
26+
<!-- Describe what the behavior would be without the bug. -->
27+
28+
**Steps to reproduce:**
29+
30+
<!-- Please explain the steps required to duplicate the issue, especially if you are able to provide a sample application. -->
31+
32+
**Related code:**
33+
34+
<!-- If you are able to illustrate the bug or feature request with an example, please provide it here. -->
35+
36+
```
37+
insert short code snippets here
38+
```
39+
40+
**Other information:**
41+
42+
<!-- List any other information that is relevant to your issue. Related issues, suggestions on how to fix, Stack Overflow links, forum links, etc. -->
Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
name: Feature Request
3+
about: Suggest an idea for this project
4+
title: "feature: "
5+
labels: "enhancement"
6+
assignees: ""
7+
8+
---
9+
10+
# Feature Request
11+
12+
**Describe the Feature Request**
13+
14+
<!-- A clear and concise description of what the feature request is. Please include if your feature request is related to a problem. -->
15+
16+
**Describe Preferred Solution**
17+
18+
<!-- A clear and concise description of what you want to happen. -->
19+
20+
**Describe Alternatives**
21+
22+
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
23+
24+
**Related Code**
25+
26+
<!-- If you are able to illustrate the bug or feature request with an example, please provide it here. -->
27+
28+
**Additional Context**
29+
30+
<!-- List any other information that is relevant to your issue. Stack traces, related issues, suggestions on how to add, use case, Stack Overflow links, forum links, screenshots, OS if applicable, etc. -->
31+
32+
**If the feature request is approved, would you be willing to submit a PR?**
33+
Yes / No _(Help can be provided if you need assistance submitting a PR)_
Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
---
2+
name: Codebase improvement
3+
about: Provide your feedback for the existing codebase. Suggest a better solution for algorithms, development tools, etc.
4+
title: "dev: "
5+
labels: "enhancement"
6+
assignees: ""
7+
8+
---

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
2+
3+
<!--- Please provide a general summary of your changes in the title above -->
4+
5+
## Pull request type
6+
7+
<!-- Please try to limit your pull request to one types, submit multiple pull requests if needed. -->
8+
9+
Please check the type of change your PR introduces:
10+
11+
- [ ] Bugfix
12+
- [ ] Feature
13+
- [ ] Code style update (formatting, renaming)
14+
- [ ] Refactoring (no functional changes, no api changes)
15+
- [ ] Build related changes
16+
- [ ] Documentation content changes
17+
- [ ] Other (please describe):
18+
19+
## What is the current behavior?
20+
21+
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
22+
23+
Issue Number: N/A
24+
25+
## What is the new behavior?
26+
27+
<!-- Please describe the behavior or changes that are being added by this PR. -->
28+
29+
## Other information
30+
31+
<!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->

0 commit comments

Comments
 (0)